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

CVE-2025-34142

MEDIUM · 6.9 CVSS v4.0 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
An XML External Entity (XXE) injection vulnerability exists in ETQ Reliance on the CG (legacy) platform within the `/resources/sessions/sso` endpoint. The SAML authentication handler processes XML input without disabling external entity resolution, allowing crafted SAML responses to invoke external entity references. This could enable attackers to retrieve sensitive files or perform server-side request forgery (SSRF). The issue was addressed by disabling external entity processing for the affected XML parser in versions SE.2025.1 and 2025.1.2.

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

ETQ Reliance on the CG (legacy) platform contains an XXE injection vulnerability in the SAML authentication handler at the `/resources/sessions/sso` endpoint. The XML parser processes SAML responses without disabling external entity resolution, allowing attackers to craft malicious XML with external entity references to read sensitive server files or perform SSRF attacks against internal resources.

MitigationUpgrade to ETQ Reliance versions SE.2025.1 or 2025.1.2 which disable external entity processing in the affected XML parser. If immediate upgrade is not possible, consider restricting access to the SAML endpoint or implementing a web application firewall.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm ETQ Reliance product installation
    Locate the ETQ Reliance installation directory and identify the product version from the application metadata, typically found in an About screen, version file, or installation manifest
    Affected if The product is ETQ Reliance on the CG/legacy platform and the version is below SE.2025.1 or 2025.1.2
  2. Verify SAML authentication is configured
    Check whether SAML single sign-on has been enabled in the ETQ Reliance administration console or configuration files. Look for SAML-related settings in the authentication or security configuration section
    Affected if SAML authentication is enabled and pointing to the /resources/sessions/sso endpoint
  3. Confirm endpoint exposure
    Attempt to access or verify the presence of the /resources/sessions/sso endpoint in the web application. This may be checked via web server configuration, exposed URLs, or application routing configuration
    Affected if The /resources/sessions/sso endpoint is accessible and processes SAML responses
  4. Compare installed version to fixed releases
    Obtain the exact version number of the installed ETQ Reliance CG platform and compare it against the fixed versions SE.2025.1 and 2025.1.2
    Affected if The installed version is lower than SE.2025.1 or 2025.1.2 (or if the version cannot be determined but the platform is the CG/legacy variant)
  5. Inspect XML parser configuration
    If accessible, examine the XML parser configuration or codebase handling SAML responses to verify whether external entity resolution has been disabled. Look for parser settings that control entity expansion or external reference handling
    Affected if The XML parser processing SAML responses allows external entity resolution or has no explicit disabling of external entities

A user is affected if they are running ETQ Reliance CG/legacy platform at a version below SE.2025.1 or 2025.1.2 with SAML authentication enabled and the /resources/sessions/sso endpoint exposed, and the XML parser does not explicitly disable external entity processing.

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 ETQ Reliance versions SE.2025.1 or 2025.1.2 which disable external entity processing in the affected XML parser. If immediate upgrade is not possible, consider restricting access to the SAML endpoint or implementing a web application firewall.

Recommended fix High confidence

SE.2025.1 or 2025.1.2

  1. 1. Identify the current installed version of ETQ Reliance on the CG (legacy) platform
  2. 2. Prior to upgrade, perform a full backup of the ETQ Reliance database and configuration files
  3. 3. Download ETQ Reliance version SE.2025.1 or 2025.1.2 from the official ETQ support portal
  4. 4. Review the upgrade guide specific to your deployment type (on-premises or hosted)
  5. 5. Execute the upgrade installer with appropriate administrative privileges
  6. 6. Verify the upgrade completed successfully by checking the application version in the About section
  7. 7. Test SAML SSO authentication functionality to confirm the fix is operational
  8. 8. Validate that external entity processing is disabled by reviewing XML parser configuration in the SAML handler

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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