CVE-2024-24813
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.64.0 and 15.0.0, SQL injection from a particular whitelisted method can result in access to data which the user doesn't have permission to access. Versions 14.64.0 and 15.0.0 contain a patch for this issue. No known workarounds are available.
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 · high confidenceSQL injection vulnerability in Frappe framework versions prior to 14.64.0 and 15.0.0 allows authenticated users to bypass permission checks through a whitelisted method, enabling unauthorized access to data they should not have permissions to view.
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.64.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.
-
Check installed Frappe versionRun `bench version` or inspect the file `apps/frappe/__init__.py` to find the version stringAffected if The version is lower than 14.64.0
-
Verify user authentication is enabledConfirm that the Frappe site has user accounts and login is enabled by checking Site Config or attempting access to the login page at /appAffected if The site allows user login, enabling authenticated users to exploit the permission bypass
-
Identify if custom whitelisted methods existReview custom app Python files for methods decorated with `@frappe.whitelist()` that query DocTypes, especially those that may access sensitive dataAffected if Custom whitelisted methods are present that could be leveraged to bypass permission checks
The environment is affected if Frappe version is below 14.64.0 and the site permits authenticated user access, allowing exploitation of the permission bypass vulnerability.
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.64.0
Upgrade Frappe to version 14.64.0 or 15.0.0 which contains the security patch; no workarounds are available.
14.64.0 (or 15.0.0 if upgrading to the major version 15 branch)
- 1. Back up your entire Frappe instance including database and all site files
- 2. Connect to your server and navigate to your Frappe bench directory (usually ~/frappe-bench)
- 3. Run `bench version` to confirm current Frappe version is below 14.64.0
- 4. Run `bench get-app frappe --branch version-14` to fetch the version-14 branch
- 5. Run `bench update --upgrade` to apply the upgrade
- 6. Alternatively, run `pip install frappe==14.64.0` for a specific version install
- 7. Run `bench migrate` after upgrade completes to apply any database migrations
- 8. Verify the upgrade was successful by running `bench version` and confirming it shows 14.64.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24813 — 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-2024-24813 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