CVE-2023-41328
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 low code web framework written in Python and Javascript. A SQL Injection vulnerability has been identified in the Frappe Framework which could allow a malicious actor to access sensitive information. This issue has been addressed in versions 13.46.1 and 14.20.0. Users are advised to upgrade. There's no workaround to fix this without upgrading.
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 allowing unauthorized access to sensitive data via malformed database queries.
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< 13.46.1>= 14.0.0, < 14.20.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 Framework versionRun 'bench version' in the Frappe installation directory, or inspect the Frappe app's version file (typically in apps/frappe/__init__.py or version.txt)Affected if Version is below 13.46.1, or between 14.0.0 and 14.20.0 (exclusive)
-
Confirm Frappe is the web framework in useVerify that the application runs on Frappe Framework by checking for the 'frappe' module in the Python environment or the presence of Frappe-related configuration files in the installationAffected if Frappe Framework is installed and running
-
Determine if database queries are processedCheck if the application processes user-supplied input through database query paths (this is inherent to Frappe's architecture - no specific config check needed)Affected if The Frappe instance handles any database operations, which is standard functionality
You are affected if your Frappe Framework version is either below 13.46.1 or falls between 14.0.0 and 14.20.0, since these versions contain the SQL injection vulnerability in malformed database query handling.
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 · scoped13.46.114.20.0
Upgrade Frappe Framework to version 13.46.1 or 14.20.0; no compensating controls available.
Upgrade to Frappe 13.46.1 (for v13.x) or Frappe 14.20.0 (for v14.x)
- Backup your Frappe database and critical data before upgrading
- Stop all Frappe services (bench, worker processes, web server)
- Upgrade Frappe to version 13.46.1 (if on major version 13) or 14.20.0 (if on major version 14) using your package manager or by pulling the updated code
- Run database migrations using 'bench migrate' or the equivalent migration command for your setup
- Verify the upgrade was successful and the SQL Injection vulnerability is resolved
- Restart all Frappe services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41328 — 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-2023-41328 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