November 18, 2026
Blind XXE with Out-of-Band Interaction via XML Parameter Entities
After completing the previous Blind XXE with OOB Interaction lab, I came across a slightly more challenging variation: Blind XXE with…
By Spoorthi
2 min read
After completing the previous Blind XXE with OOB Interaction lab, I came across a slightly more challenging variation: Blind XXE with Out-of-Band Interaction via XML Parameter Entities.
At first glance, it looked similar to the previous lab. The objective was still to confirm a Blind XXE vulnerability using Burp Collaborator. However, the difference was that traditional external entities were not enough. Instead, the lab required the use of XML parameter entities, a feature commonly overlooked during XML security testing.
Understanding the Challenge
The application accepted XML input but did not reflect any user-supplied content in its response. Regardless of the payload sent, the response remained unchanged.
This meant there was no way to directly observe whether an XXE payload had executed.
To confirm the vulnerability, we needed the target server to communicate with an external system under our control. This is where Burp Collaborator becomes invaluable.
What Are XML Parameter Entities?
Most XXE examples use general entities:
which are referenced as:
Parameter entities work differently. They are defined and referenced inside the DTD using the % symbol:
Because they are processed during DTD parsing, parameter entities can sometimes bypass restrictions that prevent normal entity usage.
Exploitation Process
- Capture the XML request in Burp Suite.
-
Open Burp Collaborator Client and copy the generated Collaborator URL.
-
Inject the XXE payload containing the Collaborator URL & send the request.
- Return to Burp Collaborator Client and click Poll now.
After polling, Burp Collaborator displayed DNS Interaction & HTTP interaction proving that the XML parser successfully processed the external parameter entity and attempted to fetch the remote resource.
Although the application's response never changed, the out-of-band interaction provided clear evidence that the XXE payload had executed.
Conclusion
This lab demonstrated how XML parameter entities can be abused to detect Blind XXE vulnerabilities through Out-of-Band interactions. Even when the application provides no visible feedback, DNS and HTTP callbacks captured by Burp Collaborator can conclusively prove that the XML parser processed attacker-controlled entities. Understanding parameter entities is an important step toward mastering advanced XXE exploitation techniques and recognizing how seemingly harmless XML functionality can become a powerful attack vector.
Remediation
To prevent XXE vulnerabilities:
- Disable DOCTYPE declarations whenever possible.
- Disable external entity resolution and parameter entity processing in XML parsers.
- Use secure parser configurations provided by Java, .NET, PHP, and Python libraries.
- Restrict outbound DNS and HTTP traffic from application servers through network egress filtering.
- Validate and sanitize XML input before processing.
- Regularly perform security assessments and review XML parser configurations.