dbcve.org
XdocreportApplication · Opensagres

CVE-2025-64087

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

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
A Server-Side Template Injection (SSTI) vulnerability in the FreeMarker component of opensagres XDocReport v1.0.0 to v2.1.0 allows attackers to execute arbitrary code via injecting crafted template expressions.

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 · high confidence

Server-Side Template Injection (SSTI) in the FreeMarker component of opensagres XDocReport versions 1.0.0 through 2.1.0 allows unauthenticated attackers to inject malicious FreeMarker template expressions into document generation workflows, leading to arbitrary code execution on the server.

MitigationUpgrade XDocReport to a version beyond 2.1.0; if immediate upgrade is not feasible, implement strict input validation or sandboxing around template rendering to prevent user-supplied data from reaching the FreeMarker engine.

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:>= 1.0.0, <= 2.1.0

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. Locate XDocReport library in the environment
    Search for opensagres XDocReport JAR files in the application classpath, lib directory, or dependency manifests (Maven pom.xml, Gradle build files)
    Affected if XDocReport library is present in the application
  2. Determine the installed XDocReport version
    Read the version from the JAR manifest, dependency declaration, or library metadata; compare against the affected range 1.0.0 to 2.1.0
    Affected if Installed version is 1.0.0, 2.1.0, or any version in between
  3. Confirm FreeMarker template rendering is in use
    Review application code for invocations of XDocReport template rendering APIs that utilize FreeMarker as the template engine
    Affected if The application performs document generation using FreeMarker-based XDocReport templates
  4. Inspect template input data flow
    Trace the data path from user inputs to the XDocReport template rendering call; determine whether unsanitized or unvalidated data reaches the template engine
    Affected if User-controlled input flows directly into the template without input validation or sandboxing

The environment is affected if XDocReport version 1.0.0 through 2.1.0 is installed and FreeMarker template rendering processes user-supplied data without validation.

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.1.0
Vendor patch github.com →
Interim mitigation

Upgrade XDocReport to a version beyond 2.1.0; if immediate upgrade is not feasible, implement strict input validation or sandboxing around template rendering to prevent user-supplied data from reaching the FreeMarker engine.

Recommended fix Moderate confidence

XDocReport version 2.1.1 or later

  1. 1. Identify all projects and dependencies that include the XDocReport library (versions 1.0.0 through 2.1.0)
  2. 2. Locate the build configuration files (pom.xml, build.gradle, or equivalent) that declare the XDocReport dependency
  3. 3. Update the XDocReport dependency version to 2.1.1 or later (e.g., change version from 2.1.0 to 2.1.1)
  4. 4. Rebuild and test the application to ensure the upgrade does not introduce regressions
  5. 5. Redeploy the updated application to all affected environments
  6. 6. Verify the FreeMarker template processing no longer allows arbitrary code execution
Caveat Review release notes for any API changes between 2.1.0 and 2.1.1, though minor version upgrades typically have minimal breaking changes

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

Fix this in Xdocreport Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64087 — 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-64087 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