CVE-2026-29077
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 15.98.0 and 14.100.0, due to a lack of validation when sharing documents, a user could share a document with a permission that they themselves didn't have. This issue has been patched in versions 15.98.0 and 14.100.0.
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 confidenceThis is an authorization bypass vulnerability in the Frappe web framework where the document sharing functionality lacks validation to ensure users can only share documents with permissions they themselves possess. A user could share a document with permissions they don't have, allowing privilege escalation through improper access control.
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.100.0>= 15.0.0, < 15.98.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
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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.
-
Identify installed Frappe versionRun 'bench version' or check the version file in your Frappe installation directory (frappe/__init__.py)Affected if Version is below 14.100.0 OR version is 15.0.0 through 15.97.x
-
Verify document sharing feature is accessibleCheck if the 'Share' action is available on documents in the Frappe desk interface, or inspect the sharing endpoint permissions in the systemAffected if Document sharing feature is enabled and accessible to users without admin restrictions
-
Confirm sharing permissions validation is missingReview the sharing logic in the codebase: check the 'share' method in document controller or sharing API handler for permission level checks before allowing share actionsAffected if The sharing code lacks validation to verify the requesting user has the same permission level they are attempting to grant to others
You are affected if your Frappe version is below 14.100.0 or between 15.0.0 and 15.97.x AND the document sharing feature is enabled and accessible to non-admin 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.100.015.98.0
Upgrade to Frappe versions 15.98.0 or 14.100.0 or later to apply the patch that adds validation to the document sharing functionality.
14.100.0 for version-14 branch; 15.98.0 for version-15 branch
- 1. Identify your current Frappe version by checking the instance or running 'bench version'
- 2. If running Frappe version 14.x (below 14.100.0), upgrade to version 14.100.0 or later using 'bench switch-to-branch version-14' followed by 'bench update --patch'
- 3. If running Frappe version 15.x (15.0.0 to 15.97.x), upgrade to version 15.98.0 or later using 'bench switch-to-branch version-15' followed by 'bench update --patch'
- 4. Verify the upgrade was successful by checking 'bench version' output
- 5. Test the document sharing functionality to confirm the fix is working
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29077 — 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-2026-29077 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