CVE-2024-27105
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.66.3 and 15.16.0, file permission can be bypassed using certain endpoints, granting less privileged users permission to delete or clone a file. Versions 14.66.3 and 15.16.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 confidenceFrappe framework versions prior to 14.66.3 and 15.16.0 contain an authorization bypass vulnerability in file operation endpoints that allows authenticated users with lower privileges to delete or clone files they should not have access to, effectively bypassing the framework's permission system for file resources.
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.66.3>= 15.0.0, < 15.16.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 framework versionQuery the Frappe instance or bench version command to retrieve the exact version number of the Frappe framework installationAffected if The installed version is below 14.66.3 or is between 15.0.0 and 15.16.0 (exclusive)
-
Identify Frappe major version branchDetermine whether the installation uses Frappe version 14.x or 15.x branch by examining the version string prefixAffected if The version falls into the 14.x branch before 14.66.3 or the 15.x branch before 15.16.0
-
Verify file operation endpoints are accessibleConfirm that file delete and clone/copy endpoints are reachable within the Frappe instance through API or web interfaceAffected if File operation endpoints exist and accept requests from authenticated users with lower privileges
-
Confirm user permission system is in useCheck that the Frappe instance has role-based permission system configured for file resourcesAffected if The permission system is active but the file operation endpoints do not properly enforce authorization checks
A user is affected if their Frappe installation version is either below 14.66.3 in the 14.x branch or between 15.0.0 and 15.16.0 in the 15.x branch, and file operation functionality is accessible to authenticated users.
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.66.315.16.0
Upgrade Frappe to version 14.66.3 or 15.16.0 or later to apply the patched access controls. No workarounds are available, so prompt patching is essential.
14.66.3 for v14.x branch; 15.16.0 for v15.x branch
- Identify the current Frappe version in use by checking the installed Frappe version
- If running Frappe version 14.x: upgrade to version 14.66.3 or later (e.g., pip install frappe==14.66.3 or equivalent package manager command)
- If running Frappe version 15.x: upgrade to version 15.16.0 or later (e.g., pip install frappe==15.16.0 or equivalent package manager command)
- After upgrading, verify the installation by checking the new Frappe version matches the target fixed release
- Test that file permission enforcement is working correctly, particularly for delete and clone file operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27105 — 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-27105 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