exploit-lfi

Detect and validate Local File Inclusion vulnerabilities via crafted URL payloads.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/0X6C7879/aegissec --skill exploit-lfi-0x6c7879
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploit-lfi
Source: https://github.com/0X6C7879/aegissec/tree/main/skills/exploit-lfi
Command: npx skills add https://github.com/0X6C7879/aegissec --skill exploit-lfi-0x6c7879

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the detection and exploitation workflow for Local File Inclusion (LFI) vulnerabilities, enabling security testers to quickly verify access to sensitive files and assess potential lateral movement vectors.

Core Features & Use Cases

  • Detect LFI vulnerability by testing common parameters and traversal payloads across Linux and Windows targets.
  • Validate PHP wrapper protocols (e.g., php://filter) to read and transform file contents.
  • Explore exploitation paths such as log poisoning, /proc/self/environ, and temporary files for RCE scenarios.
  • Provide ready-to-run payload categories and an orchestration flow to guide manual testing and reporting.

Quick Start

Target a URL with a vulnerable parameter and run traversal, wrapper, and poisoning payloads to begin testing.

Frequently Asked Questions about exploit-lfi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for local file inclusion vulnerabilities in web applications?

Detect local file inclusion by injecting traversal payloads into URL parameters and analyzing HTTP responses for indicators like root:x:0:0: or [fonts]. This verifies unauthorized file access across Linux and Windows targets.

Can I use PHP wrappers to exploit LFI and read source code?

PHP wrapper protocols like php://filter can be used during LFI exploitation to read and transform file contents. This technique helps extract PHP code that would otherwise be executed rather than displayed.

What is the best way to achieve remote code execution from an LFI vulnerability?

Remote code execution from LFI can be explored through log poisoning, /proc/self/environ reads, and temporary file manipulation. These paths inject PHP code into files that the application then includes and executes.

Does this LFI testing approach support both Linux and Windows targets?

Yes, LFI testing applies to web applications across both Linux and Windows targets. Payloads are categorized for traversal, encoding, null-byte, extension, and path confusion techniques to handle different operating system path structures.

What payload categories are available for bypassing LFI filters?

Available LFI payload categories include traversal, encoding, null-byte, extension, path confusion, and mixed techniques. These bypass filters by manipulating file paths to access sensitive system files.

Do I need the requests library to run LFI exploitation tests?

Yes, the requests library is required because the testing workflow issues HTTP requests to target URLs and parses the responses for file content and PHP code indicators to validate vulnerabilities.