skills/lfi/SKILL.md
# LFI — Local File Inclusion Bypass ## What It Does Tests LFI bypass techniques: path traversal, null bytes, wrappers, log poisoning. Load `general-security-testing-policy`, `live-testing-policy`, and `injection-testing-policy` before live testing. For file/path sinks, absence of an immediate file read or response delta is not a stop reason by itself; use the policy to reason about path normalization, extension allowlists, wrappers, encoding, parser differences, and stack-specific proof ladder
npx skillsauth add ghostonbutterbread/bug-bounty-harness skills/lfiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Tests LFI bypass techniques: path traversal, null bytes, wrappers, log poisoning.
Load general-security-testing-policy, live-testing-policy, and
injection-testing-policy before live testing. For file/path sinks, absence of
an immediate file read or response delta is not a stop reason by itself; use
the policy to reason about path normalization, extension allowlists, wrappers,
encoding, parser differences, and stack-specific proof ladders.
/lfi <target> [--param <param_name>] [--program <program>]
Uses /bypass harness: ~/projects/bug_bounty_harness/agents/bypass_harness.py
/lfi https://target.com/download?file=test.pdf
/lfi https://target.com/view?path=/etc/passwd --param path
../../etc/passwd, %2e%2e%2f%00, %2500php://filter/, data://, expect:///var/log/apache2/access.log/proc/self/environ, /proc/[pid]/fd/*documentation
Use when attacker-controlled input is saved and rendered later in a profile, comment, title, notification, admin view, export, email, feed, upload metadata, or other stored render surface.
content-media
Use when attacker-controlled input appears in the immediate HTTP response or browser-rendered page and needs reflected XSS context classification, payload selection, mutation, and browser verification.
data-ai
Use when inspecting proxy traffic from PwnFox-profiled browser sessions, filtering Caido/Burp/proxy history by X-PwnFox-Color, or interpreting user phrases like 'Red session' as a distinct browser/auth/profile lane.
tools
Use when XSS depends on browser-side sources and sinks such as URL/query/hash, router state, local/session storage, cookies, postMessage, DOM parsing, framework render paths, or client-side sanitizer behavior.