CVE-2025-30214
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.89.0 and 15.51.0, making crafted requests could lead to information disclosure that could further lead to account takeover. Versions 14.89.0 and 15.51.0 fix the issue. There's no workaround to fix this without upgrading.
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 web application framework versions prior to 14.89.0 and 15.51.0 contain an information disclosure vulnerability exploitable via crafted HTTP requests. The disclosed information can be leveraged to achieve account takeover, indicating exposure of sensitive session data, credentials, or authentication tokens.
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.89.0>= 15.0.0, < 15.51.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify installed Frappe versionRun 'bench version' or check the version file in your Frappe installation directoryAffected if The version is below 14.89.0, or is 15.x and below 15.51.0
-
Check if Frappe web server is exposedInspect your web server configuration (nginx/apache) to confirm Frappe is accessible via HTTP/HTTPSAffected if Frappe web interface is publicly or externally accessible without additional authentication layers
-
Review HTTP request handling logsExamine Frappe web logs for unusual or crafted HTTP requests that may have triggered the disclosureAffected if Logs show unexpected request patterns or evidence of information leakage
-
Verify session token storage configurationCheck the Frappe session configuration files for how tokens are handled and storedAffected if Session tokens or authentication data are stored or transmitted without proper encryption
-
Audit user account securityReview user accounts for any unauthorized access or suspicious session activityAffected if Accounts show unexpected logins, altered permissions, or compromised credentials
You are affected if your Frappe version is below 14.89.0 or between 15.0.0 and 15.51.0, and the web framework is accessible via HTTP requests that could trigger the information disclosure.
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.89.015.51.0
Upgrade Frappe to version 14.89.0 or 15.51.0 or later. No workarounds exist; immediate patching is required given the high severity and potential for account compromise.
Frappe 14.89.0 or later for v14; Frappe 15.51.0 or later for v15
- 1. Back up your current Frappe instance and database before upgrading
- 2. For Frappe version 14.x: Upgrade to version 14.89.0 or later
- 3. For Frappe version 15.x: Upgrade to version 15.51.0 or later
- 4. Use the appropriate Frappe bench upgrade command (bench update or bench migrate) after upgrading
- 5. Verify the upgrade was successful and test critical functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30214 — 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-30214 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