What is the CVSS score of CVE-2025-70614?

CVE-2025-70614 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2025-70614?

Within 24 hours: Inventory all systems running OC Messaging/USSD Gateway 6.32.2 and restrict access to the web control panel to administrative personnel only. Within 7 days: Implement network segmentation to limit control panel access by IP whitelist, enable enhanced logging/monitoring of API parameter manipulation attempts, and contact OpenCode Systems for patch timeline and interim guidance. Within 30 days: Evaluate alternative messaging platforms and establish a migration roadmap if the vendor cannot provide a timely security patch.

Opencode CVE-2025-70614

HIGH

Improper Access Control (CWE-284)

2026-03-05 cve@mitre.org

Authentication Bypass Opencode Ussd Gateway

8.1

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-284 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Access control enforcement MITRE ATT&CK 1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	CVSS 8.1 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: None. Exploitation requires authentication.
Exploit ScenarioDerived	An attacker (requires authentication) could exploit this vulnerability to compromise the affected system.

Act Now Prioritize within 24-48h. Why: Active threat signals + CRITICAL/HIGH severity.

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

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. [CVSS 8.1 HIGH]

RemediationAI

Monitor vendor advisories for a patch. Restrict network access to the affected service where possible.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-284 (Improper Access Control). 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.

Know when Opencode gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.1 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

DescriptionCVE.org

Executive ViewAI

Why It Matters

OpenCode Systems OC Messaging/USSD Gateway version 6.32.2 contains a critical access control flaw that allows authenticated users with low privileges to intercept and read SMS messages intended for other customers or tenants. This exposes sensitive communications across your messaging infrastructure and creates significant compliance and data protection risks without an available vendor patch.

Business Impact: High

Compensating Controls

Restrict web control panel access to administrative personnel via firewall/network ACLs; implement WAF rules to detect and block crafted company/tenant identifier parameters in API requests; enable detailed audit logging of all control panel access and API calls; monitor for suspicious parameter manipulation patterns; consider disabling the control panel feature if possible and managing configurations via backend systems only; implement role-based access control (RBAC) to enforce strict separation of duties.

Threat Intelligence Overview

EPSS Score

0.0%

Top 91% exploitable

Threat Intel

1 source

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS CISA

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat Yes

Deciding rule

Active threat signals + CRITICAL/HIGH severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.