The Rise and Fall of XXE and XML Security
What You'll Learn
You'll understand why XML External Entity (XXE) attacks dominated security discussions in 2017 but disappeared as a standalone category by 2021.
The XML Security Era
In the 2000s and early 2010s, XML was the lingua franca of web services. SOAP APIs, configuration files, and data exchange formats relied heavily on XML parsers. These parsers supported a powerful feature called external entities — essentially, instructions that told the parser to fetch and include content from external sources (files or URLs).
The XXE Epidemic
By 2017, XXE had become the #4 threat in the OWASP Top 10. Attackers exploited misconfigured XML parsers to:
- Read sensitive files from the server (
/etc/passwd) - Perform server-side request forgery (SSRF)
- Execute denial-of-service attacks
- Exfiltrate data
Analogy: Think of XML parsers like overly helpful assistants who, when reading a document, would fetch any reference mentioned — even if that reference was "go read my boss's private emails."
Why It Disappeared
By 2021, XXE vanished as a standalone OWASP category. Why?
- Technology shift: JSON replaced XML in modern APIs (REST over SOAP)
- Secure defaults: Modern XML libraries disabled external entity processing by default
- Developer awareness: The 2017 spotlight drove widespread fixes
- Category consolidation: Remaining XXE risks merged into broader categories like Server-Side Request Forgery (A10:2021) and Security Misconfiguration (A05:2021)
The threat didn't fully disappear — legacy systems still use XML — but its prevalence dropped dramatically enough to no longer warrant dedicated Top 10 placement.
Key Takeaway: XXE's rise and fall demonstrates how security landscapes evolve with technology adoption, secure-by-default principles, and community awareness — turning yesterday's critical vulnerability into today's niche concern.