dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2025-31497

HIGH · 7.5 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
TEIGarage is a webservice and RESTful service to transform, convert and validate various formats, focussing on the TEI format. The Document Conversion Service contains a critical XML External Entity (XXE) Injection vulnerability in its document conversion functionality. The service processes XML files during the conversion process but fails to disable external entity processing, allowing an attacker to read arbitrary files from the server's filesystem. This vulnerability could allow attackers to read sensitive files from the server's filesystem, potentially exposing configuration files, credentials, or other confidential information. Additionally, depending on the server configuration, this could potentially be used to perform server-side request forgery (SSRF) attacks by making the server connect to internal services. This issue is patched in version 1.2.4. A workaround for this vulnerability includes disabling external entity processing in the XML parser by setting the appropriate security features (e.g., XMLConstants.FEATURE_SECURE_PROCESSING).

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

TEIGarage's Document Conversion Service contains an XXE injection vulnerability where the XML parser fails to disable external entity processing, allowing attackers to read arbitrary files from the server filesystem or perform SSRF attacks via malicious XML input.

MitigationUpgrade to version 1.2.4 or disable external entity processing in the XML parser by setting XMLConstants.FEATURE_SECURE_PROCESSING=true.

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

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
None
Availability
None

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

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 TEIGarage Document Conversion Service installation
    Locate the TEIGarage application or service on the system. Check for installed packages, running services, or application directories related to Document Conversion Service.
    Affected if TEIGarage Document Conversion Service is not installed or not running
  2. Determine installed version
    Query the application for its version information using the product's native version command, configuration file, or API endpoint. Compare the version number to the fixed version 1.2.4.
    Affected if Version is lower than 1.2.4 and the service processes XML input
  3. Verify XML processing is enabled
    Check if the service accepts or processes XML documents. Inspect the service configuration or documentation to confirm XML input handling is active.
    Affected if XML document processing is enabled and the version is below 1.2.4
  4. Inspect XML parser configuration
    Examine the XML parser settings in the service configuration or source code. Look for whether external entity processing is explicitly disabled or if XMLConstants.FEATURE_SECURE_PROCESSING is set to true.
    Affected if External entity processing is not disabled in the XML parser configuration

The environment is affected if TEIGarage Document Conversion Service is installed with a version lower than 1.2.4 and the service processes XML documents with external entity processing enabled in the parser.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.2.4 or disable external entity processing in the XML parser by setting XMLConstants.FEATURE_SECURE_PROCESSING=true.

Recommended fix Moderate confidence

version 1.2.4

  1. Upgrade TEIGarage to version 1.2.4 or later to resolve the XXE vulnerability
  2. After upgrading, verify that the Document Conversion Service properly handles XML files and that external entity processing is disabled
  3. If unable to upgrade immediately, configure the XML parser to disable external entity processing by setting XMLConstants.FEATURE_SECURE_PROCESSING to true in the XML processing code

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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