CVE-2026-29081
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.100.1 and 15.100.0, an endpoint was vulnerable to SQL injection through specially crafted requests, which would allow a malicious actor to extract sensitive information. This issue has been patched in versions 14.100.1 and 15.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 confidenceFrappe framework versions prior to 14.100.1 and 15.100.0 contain a SQL injection vulnerability in a specific endpoint. Attackers can craft malicious requests to inject arbitrary SQL queries and extract sensitive database information.
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.1>= 15.0.0, <= 15.100.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.
-
Identify Frappe versionRun 'bench version' in the Frappe bench directory, or check the 'frappe' package version via 'pip show frappe' or the installed apps list in FrappeAffected if Version is less than 14.100.1, OR version is 15.0.0 through 15.100.0 (inclusive)
-
Locate the vulnerable endpointReview application routing configuration or API route definitions to identify the specific endpoint associated with this CVE. Check Frappe's route files in the app (such as api.py or web.py files in the frappe app directory)Affected if The vulnerable endpoint is exposed and accessible to the attacker
-
Verify endpoint accessibilityConfirm the endpoint is reachable from the network by checking web server configuration, firewall rules, or by reviewing which routes are registered in the Frappe application routing tableAffected if The endpoint is publicly accessible or accessible to untrusted users
-
Review application logs for suspicious SQL patternsExamine Frappe's site logs (typically in sites/[site-name]/logs/) or database query logs for unusual SQL syntax, UNION SELECT statements, or OR 1=1 patterns in request parametersAffected if Logs show SQL injection attempts or unusual query patterns matching the vulnerable endpoint
-
Check for unauthorized data accessReview database audit logs or Frappe's document change logs for unexpected SELECT queries, especially those accessing system tables like 'tabUser' or 'tabServer Script' that the legitimate application would not typically queryAffected if Unusual or unauthorized database queries are present in logs
The environment is affected if Frappe version is below 14.100.1 or between 15.0.0 and 15.100.0 inclusive, AND the vulnerable endpoint is accessible to attackers.
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.1
Upgrade Frappe to version 14.100.1 or 15.100.0 (or later) to apply the patch. If immediate upgrade is not feasible, temporarily restrict access to the vulnerable endpoint via web application firewall or network-level controls.
14.100.1 (for v14.x) or 15.100.0 (for v15.x)
- 1. Create a full backup of the database and application files before proceeding
- 2. If running Frappe version 14.x (less than 14.100.1), upgrade to version 14.100.1
- 3. If running Frappe version 15.x (between 15.0.0 and 15.100.0), upgrade to version 15.100.0
- 4. Run any database migration scripts required by the upgrade (bench migrate)
- 5. Verify the application starts successfully after the upgrade
- 6. Test the application functionality to ensure the SQL injection vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.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 $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29081 — 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-29081 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