Cyber Resilience

CVE-2025-65482

XXE in Opensagres Xdocreport 0.9.2 – 2.0.3

XXE
Published
20 January 2026
Modified
03 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0049 40th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2025-65482 is a critical-severity Improper Restriction of XML External Entity Reference (CWE-611) vulnerability in Opensagres Xdocreport. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-65482 is an XML External Entity (XXE) vulnerability, mapped to CWE-611, present in opensagres XDocReport versions from v0.9.2 to v2.0.3. Published on 2026-01-20, it allows attackers to execute arbitrary code by uploading a crafted .docx file to affected systems. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), marking it as critical due to its severe potential impact.

Any remote attacker can exploit this vulnerability without authentication, privileges, or user interaction, as it is accessible over the network with low complexity. Successful exploitation via a malicious .docx file upload enables arbitrary code execution on the target system, potentially leading to full compromise with high impacts on confidentiality, integrity, and availability.

Mitigation guidance and patches should be reviewed in the referenced advisories, including the opensagres/xdocreport GitHub repository, proof-of-concept details at github.com/AT190510-Cuong/CVE-2025-65482-XXE-, and additional analysis on hackmd.io/@cuongnh/r1B7B8fJ-g and hackmd.io/@cuongnh/rkJPCgSy-l, along with the shared folder at drive.google.com/drive/folders/1hUyCznpBN7ivo5krmyJ4OQc_q626Hy5q.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-611

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1213 Data from Information Repositories Collection
Adversaries may leverage information repositories to mine valuable information.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-64087Same product: Opensagres Xdocreport
CVE-2023-29498Shared CWE-611
CVE-2024-52596Shared CWE-611
CVE-2023-40503Shared CWE-611
CVE-2023-29443Shared CWE-611
CVE-2024-54171Shared CWE-611
CVE-2023-40239Shared CWE-611
CVE-2024-52806Shared CWE-611
CVE-2024-50848Shared CWE-611
CVE-2025-58360Shared CWE-611

Affected Assets

opensagres
xdocreport
0.9.2 — 2.0.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.1
  • V15.3.2

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings good match

Secure configuration settings can disable external entity processing in XML parsers.

SA-11 Developer Testing and Evaluation good match

Developer testing can discover XXE flaws through targeted XML parsing tests.

SI-10 Information Input Validation good match

Input validation can reject or sanitize XML containing external entity references.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Hardened XML parser configurations directly disable external entity resolution.

PR.PS-06 mostly match
prevents

Secure SDLC practices include input validation and safe XML parser configuration that prevent XXE.

ID.RA-01 partial match
prevents

Vulnerability scanning can discover XXE flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Patching eliminates XXE-vulnerable parser versions but is only one aspect of software maintenance.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches XXE via static analysis and dynamic XML fuzzing.

A.8.8 Management of technical vulnerabilities mostly match
finds

Vulnerability management identifies and patches XML libraries with unsafe default entity settings.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and entity handling that directly prevents XXE.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for disabling external entity processing in XML parsers.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include safe parser configuration that mitigates external entity risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards require disabling DTDs and external entities in XML processing.

References