What is CVE-2024-35374?

CVE-2024-35374 is a critical-severity SQL injection vulnerability in mocodo (pip), affecting versions <= 4.2.6. It is fixed in 4.2.7. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2024-35374?

CVE-2024-35374 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of mocodo are affected by CVE-2024-35374?

mocodo (pip) versions <= 4.2.6 is affected.

Is there a fix for CVE-2024-35374?

Yes. CVE-2024-35374 is fixed in 4.2.7. Upgrade to this version or later.

Is CVE-2024-35374 exploitable, and should I be worried?

Whether CVE-2024-35374 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-35374 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-35374 in mocodo

Q: How severe is CVE-2024-35374?

CVE-2024-35374 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of mocodo are affected by CVE-2024-35374?

mocodo (pip) versions <= 4.2.6 is affected.

Q: Is there a fix for CVE-2024-35374?

Yes. CVE-2024-35374 is fixed in 4.2.7. Upgrade to this version or later.

Q: Is CVE-2024-35374 exploitable, and should I be worried?

Whether CVE-2024-35374 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-35374 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-35374?

Upgrade mocodo to 4.2.7 or later.

Summary

Mocodo vulnerable to SQL injection in /web/generate.php

Mocodo Mocodo Online 4.2.6 and below does not properly sanitize the sql_case input field in /web/generate.php, allowing remote attackers to execute arbitrary SQL commands and potentially command injection, leading to remote code execution (RCE) under certain conditions.

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2024-35374 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.2.7); upgrading removes the vulnerable code path.

Affected versions

mocodo (<= 4.2.6)

Security releases

mocodo → 4.2.7 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade mocodo to 4.2.7 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-35374? CVE-2024-35374 is a critical-severity SQL injection vulnerability in mocodo (pip), affecting versions <= 4.2.6. It is fixed in 4.2.7. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2024-35374? CVE-2024-35374 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of mocodo are affected by CVE-2024-35374? mocodo (pip) versions <= 4.2.6 is affected.
Is there a fix for CVE-2024-35374? Yes. CVE-2024-35374 is fixed in 4.2.7. Upgrade to this version or later.
Is CVE-2024-35374 exploitable, and should I be worried? Whether CVE-2024-35374 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-35374 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-35374? Upgrade mocodo to 4.2.7 or later.