Skip to main content
VulnerabilityPublished Updated

CVE-2025-64087: xdocreport · Template Injection

Affects xdocreportSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.opensagres/xdocreportpkg:maven/org.opensagres/xdocreportOther threatsAffected
  • =1.0.0
  • =2.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor for and apply official patches or updates from opensagres XDocReport as soon as they become available.
  2. Until patches are released, restrict access to template editing interfaces to trusted administrators only.
  3. Implement strict input validation and sanitization on all user-supplied template data to prevent injection of malicious expressions.
  4. Employ sandboxing techniques for template processing to limit the execution scope and prevent arbitrary code execution.
  5. Conduct code reviews and security assessments of any custom templates or integrations using FreeMarker to identify unsafe patterns.
  6. Use network segmentation and firewall rules to limit exposure of systems running vulnerable versions.
  7. Deploy runtime application self-protection (RASP) or web application firewalls (WAF) with rules targeting SSTI attack patterns.
  8. Increase monitoring and logging around document generation services to detect anomalous template processing or execution behaviors.
  9. Educate developers and administrators about the risks of SSTI vulnerabilities and secure template handling practices.
  10. Prepare incident response plans specifically addressing potential exploitation scenarios involving template injection.

Description

CVE-2025-64087 is a critical Server-Side Template Injection (SSTI) vulnerability in the FreeMarker component used by opensagres XDocReport versions 1.0.0 to 2.1.0. This flaw allows unauthenticated remote attackers to execute arbitrary code on affected systems by injecting malicious template expressions. The vulnerability has a CVSS score of 9.8, indicating a high impact on confidentiality, integrity, and availability without requiring user interaction or privileges. Although no known exploits are currently in the wild, the ease of exploitation and severity make it a significant threat. European organizations using XDocReport for document generation or reporting are at risk, especially those in sectors with high reliance on automated document processing.

References

Community reviews

Loading reviews…