Cyber Resilience

CVE-2025-33025

Published
13 May 2025
Modified
17 June 2026
CVSS Score v4 9.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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
EPSS Score 0.012 65th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-33025 is a critical-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability. Its CVSS base score is 9.4 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 35% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All versions < V2.16.5), RUGGEDCOM ROX RX1400 (All versions < V2.16.5), RUGGEDCOM ROX RX1500 (All versions < V2.16.5), RUGGEDCOM ROX RX1501 (All versions <…

more

V2.16.5), RUGGEDCOM ROX RX1510 (All versions < V2.16.5), RUGGEDCOM ROX RX1511 (All versions < V2.16.5), RUGGEDCOM ROX RX1512 (All versions < V2.16.5), RUGGEDCOM ROX RX1524 (All versions < V2.16.5), RUGGEDCOM ROX RX1536 (All versions < V2.16.5), RUGGEDCOM ROX RX5000 (All versions < V2.16.5). The 'traceroute' tool in the web interface of affected devices is vulnerable to command injection due to missing server side input sanitation. This could allow an authenticated remote attacker to execute arbitrary code with root privileges.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-56694Shared CWE-602
CVE-2024-31491Shared CWE-602
CVE-2024-23666Shared CWE-602
CVE-2025-2139Shared CWE-602
CVE-2025-47697Shared CWE-602
CVE-2025-51682Shared CWE-602
CVE-2023-39218Shared CWE-602
CVE-2026-11092Shared CWE-602
CVE-2026-13896Shared CWE-602
CVE-2026-11267Shared CWE-602

Affected Assets

All
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.7.1
  • V2.2.2
  • V8.3.1
  • V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

Requires a tamper-proof, always-invoked reference monitor that cannot be bypassed by client-side logic.

Enforces all access decisions on the server according to policy rather than trusting client-supplied enforcement.

Enforces information-flow rules at the server boundary instead of delegating them to the client.

Monitors and controls all external and key internal interfaces so that server-side policy cannot be off-loaded to clients.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.

PR.AA-05 partial match
prevents

Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure architecture principles discourage client-side trust but do not directly address this weakness.

finds

Security testing can detect client-side enforcement but is not the primary mitigation.

prevents

Information access restriction is undermined when the client is trusted to enforce it.

prevents

Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.

prevents

Application security requirements explicitly call for server-side enforcement of security mechanisms.

prevents

Secure coding standards require server-side checks and reject client-only enforcement.

References