hunt-xxe

Identify XXE vulnerabilities in XML parsers via inline and DTD payloads.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sseshachala/Claude-BugHunter-archive --skill hunt-xxe-sseshachala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-xxe
Source: https://github.com/sseshachala/Claude-BugHunter-archive/tree/main/skills/hunt-xxe
Command: npx skills add https://github.com/sseshachala/Claude-BugHunter-archive --skill hunt-xxe-sseshachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

XXE vulnerabilities in XML parsers allow attackers to read local files, leak sensitive configuration data, or exfiltrate data via external entity references when parsing untrusted XML input.

Core Features & Use Cases

  • Detects and analyzes external entity expansion behavior across common XML processing paths (SOAP, OOXML, SVG, and XML-in API workflows).
  • Documents exploitation chains from in-band file reads to blind OOB callbacks and SSRF-like paths, with evidence and remediation guidance.
  • Supports a structured approach to assessing parser hardening and validating mitigation effectiveness in bug-bounty and red-team engagements.

Quick Start

Analyze an XML endpoint by injecting an inline DOCTYPE with an ENTITY and observe whether the payload expands or triggers external callbacks; then repeat with blind payloads and log any outbound interactions.

Frequently Asked Questions about hunt-xxe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for XXE vulnerabilities in XML parsers?

To test for XXE vulnerabilities, inject an inline DOCTYPE with an ENTITY into XML input and observe whether the payload expands or triggers external callbacks. Repeating this with blind payloads and logging outbound interactions confirms the vulnerability.

What is a blind XXE vulnerability and how does out-of-band exfiltration work?

Blind XXE occurs when an XML parser processes external entities but returns no direct response. Out-of-band exfiltration works by using DTD-based payloads to force the parser to send sensitive data to an attacker-controlled external callback endpoint.

Can I use XML payloads to find SSRF chains in SOAP or OOXML endpoints?

Yes, testing SOAP and OOXML endpoints with external entity payloads can reveal SSRF-like paths. By injecting DTD-based payloads, you can force the XML parser to make outbound requests, confirming server-side request forgery chains.

Does this XML vulnerability testing approach work for SVG and XML-in API workflows?

Yes, this approach applies to SVG and XML-in API workflows. It analyzes external entity expansion behavior across common XML processing paths to detect in-band file reads or blind out-of-band data exfiltration in these formats.

What is the best way to verify blind out-of-band callbacks during bug bounty testing?

The best way to verify blind out-of-band callbacks is by injecting blind payloads into the target XML input and logging any outbound DNS or HTTP interactions. This OOB callback verification confirms the XXE impact without requiring direct application responses.

When should I not use inline entity probes for XML parser assessments?

Avoid inline entity probes when the target parser is hardened against external entity expansion, as they will fail to trigger in-band reads. In these cases, blind DTD-based payloads and out-of-band callback verification are required to confirm parser hardening and mitigation effectiveness.