dbcve.org
Ussd GatewayApplication · Opencode

CVE-2025-70614

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
OpenCode Systems OC Messaging / USSD Gateway OC Release 6.32.2 contains a broken access control vulnerability in the web-based control panel allowing authenticated low-privileged attackers to gain to access to arbitrary SMS messages via a crafted company or tenant identifier parameter.

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

Broken access control (IDOR) vulnerability in OpenCode Systems OC Messaging/USSD Gateway v6.32.2 web control panel allows authenticated low-privilege users to access arbitrary SMS messages by manipulating the company or tenant identifier parameter in requests, bypassing intended scope restrictions.

MitigationImplement and enforce proper authorization checks to verify that the authenticated user has legitimate access to the requested company/tenant's SMS messages before returning any data.

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
Ussd GatewayApplication
Affected:= 6.32.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 OpenCode USSD Gateway installation
    Locate the OpenCode OC Messaging/USSD Gateway installation directory or check running services for 'ocussd' or 'opencode' processes. Check for the web control panel endpoint (typically on ports 8080, 8443, or 443).
    Affected if The software is present and the web control panel is accessible on the network.
  2. Verify the installed version
    Check the version of the installed OpenCode USSD Gateway. Common methods: review the 'about' page in the web control panel, check the software release notes or version file in the installation directory, or query the application's API endpoint for version information.
    Affected if The installed version is exactly 6.32.2.
  3. Confirm web control panel is enabled
    Access the web control panel login page. Verify that the messaging/USSd gateway web interface is accessible and functional by logging in with a low-privilege user account.
    Affected if The web control panel is accessible and allows user authentication.
  4. Identify the vulnerable parameter
    Inspect HTTP requests when accessing SMS messages through the control panel. Look for parameters related to company, tenant, organization, or identifier in the request URL or body (such as 'company_id', 'tenant_id', 'org_id', or similar).
    Affected if Requests to view SMS messages contain a manipulable company/tenant identifier parameter.
  5. Test for IDOR vulnerability
    Log in as a low-privilege user assigned to one company/tenant. Attempt to access SMS messages by modifying the company/tenant identifier parameter in the request to reference a different company/tenant's data. Observe if the application returns messages from the unauthorized scope.
    Affected if The application returns SMS messages from a company/tenant different from the one the user is assigned to, confirming the IDOR flaw exists.

You are affected if the OpenCode USSD Gateway web control panel is running version 6.32.2 and a low-privilege user can access SMS messages from other companies/tenants by manipulating the identifier parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement and enforce proper authorization checks to verify that the authenticated user has legitimate access to the requested company/tenant's SMS messages before returning any data.

Fix this in Ussd Gateway Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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