CVE-2026-32954
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 · uneditedERP is a free and open source Enterprise Resource Planning tool. In versions prior to 16.8.0 and 15.100.0, certain endpoints were vulnerable to time-based and boolean-based blind SQL injection due to insufficient parameter validation, allowing attackers to infer database information. This issue has been fixed in versions 15.100.0 and 16.8.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 confidenceThe ERP application versions prior to 15.100.0 and 16.8.0 contain SQL injection vulnerabilities in certain endpoints due to insufficient parameter validation. Attackers can exploit this by sending specially crafted requests using time-based and boolean-based blind SQL injection techniques to infer database structure and contents.
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< 15.100.0>= 16.0.0, < 16.8.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 ERPNext versionRun 'bench version' command or check the version file in your Frappe/ERPNext installation directory (typically in the apps/erpnext folder or via the system database version table)Affected if The version cannot be determined or is not visible through standard Frappe commands
-
Compare version against affected rangesReview the identified version number against the affected ranges: versions less than 15.100.0 OR versions 16.0.0 through 16.7.xAffected if The installed version is < 15.100.0 OR is >= 16.0.0 but < 16.8.0
-
Determine application network exposureCheck if the ERP application is accessible from untrusted network locations (public internet or unauthorized internal networks) by reviewing firewall rules, reverse proxy configurations, and network ACLsAffected if The application is exposed to network attackers without proper authentication barriers
-
Review application logs for suspicious SQL patternsExamine Frappe/ERPNext application logs (site-specific logs in logs/ folder or database audit logs) for unusual time delays or SQL syntax patterns in request parameters that may indicate SQL injection testingAffected if Logs show time-based blind SQL injection patterns or unusual SQL syntax in request parameters
You are affected if your Frappe ERPNext installation version is less than 15.100.0 or falls between 16.0.0 and 16.7.x inclusive, and the application is network-accessible to potential 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 · scoped15.100.016.8.0
Upgrade the ERP installation to version 15.100.0 or 16.8.0 or later to apply the patch that adds proper parameter validation to prevent SQL injection.
ERPNext 15.100.0 (for v15.x) or 16.8.0 (for v16.x)
- Back up your ERPNext database and application data before upgrading
- Identify your current ERPNext version (15.x or 16.x)
- For ERPNext version 15.x: Upgrade to version 15.100.0 or later
- For ERPNext version 16.x: Upgrade to version 16.8.0 or later
- After upgrade, verify the application runs correctly and test critical business workflows
- Review release notes for any security-related changes in the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32954 — 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-32954 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