What is CVE-2025-30213?

CVE-2025-30213 is a medium-severity improper input validation vulnerability in frappe (pip), affecting versions < 14.91.0. It is fixed in 14.91.0, 15.52.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

Which versions of frappe are affected by CVE-2025-30213?

frappe (pip) versions < 14.91.0 is affected.

Is there a fix for CVE-2025-30213?

Yes. CVE-2025-30213 is fixed in 14.91.0, 15.52.0. Upgrade to this version or later.

Is CVE-2025-30213 exploitable, and should I be worried?

Whether CVE-2025-30213 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-2025-30213 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-2025-30213?

Upgrade: frappe to 14.91.0 or later, frappe to 15.52.0 or later.

CVE-2025-30213 in frappe

Q: Which versions of frappe are affected by CVE-2025-30213?

frappe (pip) versions < 14.91.0 is affected.

Q: Is there a fix for CVE-2025-30213?

Yes. CVE-2025-30213 is fixed in 14.91.0, 15.52.0. Upgrade to this version or later.

Q: Is CVE-2025-30213 exploitable, and should I be worried?

Whether CVE-2025-30213 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-2025-30213 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-2025-30213?

Upgrade: frappe to 14.91.0 or later, frappe to 15.52.0 or later.

Summary

Frappe has Possibility of Remote Code Execution due to improper validation

Workarounds

There's no workaround, an upgrade is required.

Credits

Thanks to Thanh of Calif.io for reporting the issue

Impact

A system user was able to create certain documents in a specific way that could lead to RCE.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

frappe (< 14.91.0) frappe (>= 15.0.0, < 15.52.0)

Security releases

frappe → 14.91.0 (pip) frappe → 15.52.0 (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 the following packages to resolve this vulnerability:

frappe to 14.91.0 or later; frappe to 15.52.0 or later

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

Frequently Asked Questions

What is CVE-2025-30213? CVE-2025-30213 is a medium-severity improper input validation vulnerability in frappe (pip), affecting versions < 14.91.0. It is fixed in 14.91.0, 15.52.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
Which versions of frappe are affected by CVE-2025-30213? frappe (pip) versions < 14.91.0 is affected.
Is there a fix for CVE-2025-30213? Yes. CVE-2025-30213 is fixed in 14.91.0, 15.52.0. Upgrade to this version or later.
Is CVE-2025-30213 exploitable, and should I be worried? Whether CVE-2025-30213 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-2025-30213 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-2025-30213?
- Upgrade frappe to 14.91.0 or later
- Upgrade frappe to 15.52.0 or later

Other vulnerabilities in frappe

CVE-IDSeverityPackage summary

CVE-2025-30217Mediumfrappe: Frappe has possibility of SQL injection due to improper validations CVE-2025-30214Highfrappe: Frappe vulnerable to information disclosure leading to account takeover CVE-2025-30212Mediumfrappe: Frappe has possibility of SQL injection due to improper validations