Cyber Resilience

CVE-2024-35373

Mocodo Online ≤ 4.2.6

Public PoC
Published
24 May 2024
Modified
10 June 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.012 65th percentile
Risk Priority 77 floored blend · peak EPSS

Summary

CVE-2024-35373 is a critical-severity Special Element Injection (CWE-75) vulnerability in Mocodo Mocodo Online. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 35% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Mocodo Mocodo Online 4.2.6 and below is vulnerable to Remote Code Execution via /web/rewrite.php.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
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.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-35374Same product: Mocodo Mocodo Online
CVE-2021-22911Shared CWE-75
CVE-2024-31809Shared CWE-75
CVE-2024-31812Shared CWE-75
CVE-2026-29042Shared CWE-75
CVE-2026-54771Shared CWE-75
CVE-2025-50213Shared CWE-75
CVE-2024-58362Shared CWE-75
CVE-2026-31908Shared CWE-75
CVE-2024-31806Shared CWE-75

Affected Assets

mocodo
mocodo online
≤ 4.2.6

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly stops special-element injection by rejecting or sanitizing untrusted data before it reaches a different control plane.

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 require input sanitization to block special-element injection.

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.

finds

Security testing catches injection vulnerabilities but does not itself implement the sanitization fix.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

prevents

Secure development life cycle mandates input validation and sanitization practices that directly prevent special-element injection.

prevents

Application security requirements explicitly call for controls against injection flaws including special-element handling.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe the actual sanitization logic.

prevents

Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.

References