Code execution via enabled XSLT extension functions
Published Oct 17, 2025 · Updated Oct 17, 2025
Code execution in XMLUnit for Java before 2.10.0 allows attackers to run code through an untrusted XSLT stylesheet. TransformerFactoryConfigurer.Default disables DTD loading but leaves XSLT extension functions enabled, so a supplied stylesheet can invoke processor-supported extension code. Exploitation requires control of the stylesheet and a processor configured to execute extensions; network exposure depends on the consuming application.
Summary
What happened
Code execution in XMLUnit for Java before 2.10.0 allows attackers to run code through an untrusted XSLT stylesheet. TransformerFactoryConfigurer.Default disables DTD loading but leaves XSLT extension functions enabled, so a supplied stylesheet can invoke processor-supported extension code. Exploitation requires control of the stylesheet and a processor configured to execute extensions; network exposure depends on the consuming application.
The record
- CVE
- CVE-2024-31573
- Published
- Oct 17, 2025
- Updated
- Oct 17, 2025
- Vendor
- XMLUnit
- Product
- XMLUnit for Java
- Classifications
- CWE-669
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 17, 2025CVE publishedPublication date reported by the CVE source.
- Oct 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Issue 264 proof-of-concept programproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo