Skip to content

Responsible use policy

This site documents XML External Entity injection so that security professionals can test systems they are authorized to assess and so that developers can harden their XML parsers. It exists to help defenders.

Authorized testing only

Only test systems that you own, or for which you hold explicit, written permission — a signed penetration-testing agreement, a bug bounty program's scope, or an equivalent authorization. The scope of that permission defines what you may do; nothing on this site widens it.

It is illegal to attack systems without permission

Accessing or interfering with computer systems without authorization is a crime in most jurisdictions (for example the Computer Fraud and Abuse Act in the United States, the Computer Misuse Act in the United Kingdom, and comparable laws elsewhere). Reading data via XXE, reaching internal services through SSRF, or causing a denial of service against systems you do not control can carry serious criminal and civil liability.

Defender-first by design

Every technique on this site is paired with detection guidance and a concrete remediation. If you are here to fix a vulnerability, start with the parser hardening guides: disabling DOCTYPE and external entities in your XML parser closes the entire attack class.

Test safely

  • Use lab targets or dedicated staging environments where possible.
  • Prefer benign proof-of-concept files (for example reading a known, non-sensitive file) over exfiltrating real data.
  • Avoid denial-of-service payloads such as entity-expansion bombs against shared or production systems.
  • Report findings through the proper disclosure channel and give the owner time to fix them.

Disclaimer

This material is provided for lawful security testing and educational purposes only, with no warranty. You are solely responsible for how you use it and for ensuring your testing is authorized and legal.