Responsible use and testing boundaries
This site documents Local File Inclusion and path traversal for authorized security testing and secure development. The responsible use and testing boundaries below are not optional etiquette — testing a system without authorization is illegal in most jurisdictions, regardless of intent. Read this before using anything here.
Get authorization first
- Only test systems you own or have explicit, written permission to test — a signed engagement, a bug bounty program's published scope, a CTF, or your own lab.
- Written scope beats verbal agreement. Keep the authorization document and its dates for the whole engagement.
- Unauthorized testing can violate laws such as the Computer Fraud and Abuse Act (US), the Computer Misuse Act (UK), and equivalents elsewhere, as well as the GDPR when personal data is exposed.
Stay in scope
- Test only the hosts, applications and parameters named in your authorization. Do not pivot to systems that are merely reachable.
- Bug bounty scope is binding: out-of-scope targets, denial of service, and social engineering are usually prohibited unless explicitly allowed.
- Prefer the least intrusive proof. A read of a benign marker file (for example
/etc/hostname) demonstrates the bug without touching sensitive data.
Handle data and impact carefully
- Do not exfiltrate, read or store more than needed to prove impact. Stop at the minimum that confirms the vulnerability.
- Never read or copy third-party personal data, credentials or secrets beyond what is required, and never retain them after the engagement.
- Chaining LFI to remote code execution (log poisoning, wrappers, filter chains) is high-impact and often destructive — only attempt it when your authorization clearly covers it, and avoid changing or deleting anything on the target.
Report and disclose responsibly
- Report findings promptly through the agreed channel with clear reproduction steps and the remediation guidance so the owner can fix them.
- Follow coordinated disclosure timelines; do not publish details before a fix is available unless the program permits it.
- Pair every finding with the fix. The remediation guide and the per-technique remediation sections exist for exactly this.
For developers and defenders
If you are here to fix the bug rather than test for it, you are the primary audience. Start with the remediation guide, then read the technique that matches your code pattern. Every technique page explains how to detect the attack in logs and code and how to fix it with safe APIs, canonicalization and allowlisting.
This page is general guidance, not legal advice. Laws vary by jurisdiction; when in doubt, consult a qualified professional before testing.