dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-34140

HIGH · 8.7 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 →
96/100
Remediation priority · Urgent
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 authorization bypass vulnerability exists in ETQ Reliance (legacy CG and NXG SaaS platforms). By appending a specific URI suffix to certain API endpoints, an unauthenticated attacker can bypass access control checks and retrieve limited sensitive resources. The root cause was a misconfiguration in API authorization logic, which has since been corrected in 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 · moderate confidence

ETQ Reliance (legacy CG and NXG SaaS platforms) contains an authorization bypass vulnerability where appending a specific URI suffix to certain API endpoints allows unauthenticated attackers to bypass access control checks and retrieve limited sensitive resources. The root cause is a misconfiguration in the API authorization logic that fails to properly validate access rights when the specific URI suffix is present.

MitigationUpgrade to SE.2025.1 or 2025.1.2 which contains the corrected API authorization logic. Organizations unable to upgrade immediately should review API endpoint configurations and implement additional access control validation at the gateway or WAF layer.

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:H/VI:N/VA:N/SC:N/SI:N/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 variant
    Identify whether the environment uses ETQ Reliance legacy CG platform or NXG SaaS platform. Check product documentation, installation files, or admin console for product name and platform type.
    Affected if The environment is running ETQ Reliance legacy CG or NXG SaaS platforms (as opposed to newer versions with corrected configuration).
  2. Determine installed version
    Locate the version number through the product's admin interface, command-line tool, or version file. Common paths include the About section in the UI, a version.txt file, or running 'reliance --version' if a CLI is available.
    Affected if The installed version is prior to the corrected configuration release (compare against SE.2025.1 or 2025.1.2 and later as reference points).
  3. Identify accessible API endpoints
    Review the API documentation or enumerate exposed API endpoints. Look for endpoints under paths such as /api/v1/, /api/v2/, or platform-specific API base URLs.
    Affected if API endpoints exist that handle sensitive resources and accept URI parameters.
  4. Test URI suffix bypass
    Attempt accessing a known sensitive API endpoint with an appended URI suffix pattern (such as /../, /..;, or other path traversal-like suffixes) without providing authentication credentials. Observe if the request returns successful access to resources.
    Affected if Appending a specific URI suffix to API endpoints returns sensitive data or functionality without requiring authentication, indicating the authorization bypass is present.

The environment is affected if it runs ETQ Reliance legacy CG or NXG SaaS platforms with a version prior to the corrected configuration release and the URI suffix bypass test successfully accesses protected resources without credentials.

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 SE.2025.1 or 2025.1.2 which contains the corrected API authorization logic. Organizations unable to upgrade immediately should review API endpoint configurations and implement additional access control validation at the gateway or WAF layer.

Recommended fix Moderate confidence

SE.2025.1 or 2025.1.2

  1. Identify the current version of ETQ Reliance (legacy CG or NXG SaaS platform) currently deployed
  2. Upgrade ETQ Reliance to version SE.2025.1 or version 2025.1.2 as specified in the security advisory
  3. Verify the upgrade was successful by confirming the new version number
  4. Test that the API authorization logic is functioning correctly by verifying that unauthenticated requests to sensitive endpoints are now properly denied

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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