Skip to content

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

Stay in scope

Handle data and impact carefully

Report and disclose responsibly

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.