CVE-2025-30213
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFrappe is a full-stack web application framework. Prior to versions 14.91.0 and 15.52.0, a system user was able to create certain documents in a specific way that could lead to remote code execution. Versions 14.9.1 and 15.52.0 contain a patch for the vulnerability. There's no workaround; an upgrade is required.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceFrappe framework versions prior to 14.91.0 and 15.52.0 contain a vulnerability where system users could create certain documents in a specific manner that leads to remote code execution. The vulnerability stems from improper handling of document creation that allows arbitrary code execution. Upgrading to the patched versions is required as no workarounds exist.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 14.91.0>= 15.0.0, < 15.52.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Frappe version fileFind the version.py or apps.txt file in your Frappe installation directory, typically at /frappe-bench/apps/frappe or check the output of 'bench version' commandAffected if The displayed version is below 14.91.0 or is 15.x and below 15.52.0
-
Check Python executable versionRun 'python3 --version' and verify the Frappe bench is using a supported Python version as per your Frappe installationAffected if Python version is unrelated to this CVE - this check confirms a valid Frappe environment exists
-
Identify Frappe branchRun 'bench get-app frappe' or check your frappe-bench/apps/frappe folder to determine if you are on version 14 or version 15 branchAffected if The branch is 14.x and version < 14.91.0, OR branch is 15.x and version < 15.52.0
-
Verify document creation modules existConfirm the Frappe installation has document creation capabilities by checking that the 'frappe.model.doc' module is present in the installationAffected if The module exists and the version falls within the affected ranges, the installation is vulnerable to RCE through document creation
You are affected if your Frappe installation shows a version below 14.91.0 on the version 14 branch, or below 15.52.0 on the version 15 branch.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped14.91.015.52.0
Upgrade Frappe to version 14.91.0 or 15.52.0 (depending on your major version branch) to patch the RCE vulnerability. No workarounds are available; immediate upgrade is critical given the high CVSS score of 8.8.
Upgrade to Frappe version 14.91.0 (for v14.x users) or version 15.52.0 (for v15.x users)
- 1. Backup your current Frappe database and application files
- 2. Identify your current Frappe version using `bench version` or checking your version in the Frappe framework
- 3. If running Frappe version 14.x: Upgrade to version 14.91.0 or later by running `bench switch-to-branch version-14` followed by `bench update --reset`
- 4. If running Frappe version 15.x: Upgrade to version 15.52.0 or later by running `bench switch-to-branch version-15` followed by `bench update --reset`
- 5. Verify the upgrade was successful by checking `bench version`
- 6. Test critical functionality to ensure the application works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data