XDocReport affected by an XML External Entity (XXE) vulnerabilityGHSA-7jc7-g598-2p64
CRITICALFix: opensagres/xdocreport@d9b90aeGHSA-7jc7-g598-2p64 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in fr.opensagres.xdocreport:fr.opensagres.xdocreport.document. A fix is available for fr.opensagres.xdocreport:fr.opensagres.xdocreport.document — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7jc7-g598-2p64.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
fr.opensagres.xdocreport:fr.opensagres.xdocreport.documentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An XML External Entity (XXE) vulnerability in opensagres XDocReport v0.9.2 to v2.0.3 allows attackers to execute arbitrary code via uploading a crafted .docx file.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | fr.opensagres.xdocreport:fr.opensagres.xdocreport.document | ≥ 0.9.2&&< 2.0.4 | 2.0.4fr.opensagres.xdocreport:fr.opensagres.xdocreport.document:2.0.4 |
Affected Products
xdocreportopensagresDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fr.opensagres.xdocreport:fr.opensagres.xdocreport.document, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fr.opensagres.xdocreport:fr.opensagres.xdocreport.document to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jc7-g598-2p64 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-7jc7-g598-2p64 in your dependencies?
Find it across Maven, including transitive dependencies.