hunt-lfi

Detect and validate LFI, RFI, and Path Traversal vulnerabilities in software systems.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/bpnrockstar/UnifiedBugHunter --skill hunt-lfi-bpnrockstar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-lfi
Source: https://github.com/bpnrockstar/UnifiedBugHunter/tree/main/skills/hunt-lfi
Command: npx skills add https://github.com/bpnrockstar/UnifiedBugHunter --skill hunt-lfi-bpnrockstar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill detects and validates Local File Inclusion (LFI), Remote File Inclusion (RFI), and Path Traversal vulnerabilities, identifying security weaknesses in software and systems.

Core Features & Use Cases

  • Local File Inclusion Detection: Identifies where an application may include local files leading to potential code execution or data exposure.
  • Remote File Inclusion Detection: Identifies conditions for remote code execution through the inclusion of remote files into application logic.
  • Path Traversal Detection: Detects where an application may allow access to unauthorized system files through malicious inputs.
  • Use Case: This Skill can be utilized by security analysts or developers to assess the security of a web application for critical vulnerabilities like Remote Code Execution (RCE) and information disclosure.

Quick Start

Execute the hunt-lfi skill to begin a vulnerability assessment of the target application.

Frequently Asked Questions about hunt-lfi

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

FAQPage Schema
How do I detect Local File Inclusion and Path Traversal vulnerabilities in my application?

To detect Local File Inclusion and Path Traversal vulnerabilities, you can run an assessment that attempts to read local files and traverse application-defined file system boundaries using malicious inputs. This identifies potential code execution or data exposure risks.

What is the difference between LFI and Remote File Inclusion in web application security?

LFI involves including local files into application logic, potentially exposing sensitive data, whereas Remote File Inclusion (RFI) involves including remote files, which typically leads directly to remote code execution. Both stem from malicious input handling misconfigurations.

How can I validate if a Path Traversal vulnerability leads to Remote Code Execution?

You can validate if a Path Traversal vulnerability leads to Remote Code Execution by attempting to include remote files into the application logic. Successfully including a remote file confirms conditions for RCE and critical code execution vulnerabilities.

Do I need any dependencies or scripts to scan for RFI vulnerabilities?

No external dependencies are required to scan for RFI vulnerabilities. The assessment operates using built-in scripts to detect conditions where malicious inputs allow remote files to be included, validating remote code execution risks without extra setup.

What's the best way to find file system boundary misconfigurations in software systems?

The best way to find file system boundary misconfigurations is to scan for malicious inputs that traverse application-defined directories. This detects unauthorized access to system files and highlights critical security weaknesses in the software.