dbcve.org
XdocreportApplication · Opensagres

CVE-2025-65482

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

opensagres XDocReport versions 0.9.2 through 2.0.3 contain an XXE vulnerability in .docx file parsing that allows attackers to inject malicious external entity references into XML documents, potentially leading to arbitrary code execution through server-side request forgery or file system access.

MitigationUpgrade to a patched version of XDocReport if available, or disable external entity resolution in the XML parser configuration used by the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XdocreportApplication
Affected:>= 0.9.2, <= 2.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify XDocReport installation
    Search for xdocreport JAR files in the application's classpath, lib directory, or dependencies (Maven pom.xml, Gradle build files). Common paths: WEB-INF/lib/, lib/, or build dependencies.
    Affected if XDocReport library is present in the application
  2. Check installed version
    Examine the xdocreport JAR filename or the dependency declaration for the exact version number. For Maven: grep -i 'xdocreport' pom.xml. For JARs: ls xdocreport*.jar
    Affected if Version is >= 0.9.2 and <= 2.0.3
  3. Verify .docx parsing usage
    Search codebase for imports of XDocReport docx conversion classes (e.g., XWPFConverter, DocxToXmlConverter) or code that loads .docx files using XDocReport APIs.
    Affected if Application code parses .docx files using XDocReport
  4. Inspect XML parser configuration
    Check XML parser initialization code for DocumentBuilderFactory or XMLStreamReader configuration. Look for whether FEATURE_SECURE_PROCESSING is set and whether external entity resolution has been explicitly disabled.
    Affected if External entity resolution is not explicitly disabled in the XML parser (parser uses default vulnerable configuration)

You are affected if XDocReport version 0.9.2-2.0.3 is present AND your application parses .docx files using XDocReport AND the XML parser has not had external entity resolution disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.3
Interim mitigation

Upgrade to a patched version of XDocReport if available, or disable external entity resolution in the XML parser configuration used by the application.

Recommended fix Moderate confidence

XDocReport 2.0.4 or latest stable release (check https://github.com/opensagres/xdocreport/releases)

  1. 1. Identify all Maven/Gradle dependencies referencing 'fr.opensagres.xdocreport' with versions between 0.9.2 and 2.0.3
  2. 2. Update the dependency version to 2.0.4 or later in your pom.xml (Maven) or build.gradle (Gradle)
  3. 3. Rebuild and test your application to ensure the upgrade does not break existing functionality
  4. 4. Re-scan or re-pentest to verify the XXE vulnerability is no longer present
Caveat Review release notes for 2.0.4+ as there may be minor API changes or deprecated features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xdocreport Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65482 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data