dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-41581

MEDIUM · 6.9 CVSS v4.0 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Frappe is a full-stack web application framework. Prior to versions 15.106.0 and 16.16.0, there is a possible SQL Injection via get_blog_list. This issue has been patched in versions 15.106.0 and 16.16.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 confidence

Frappe framework versions prior to 15.106.0 and 16.16.0 contain a SQL injection vulnerability in the get_blog_list function. Attackers can exploit this to inject malicious SQL queries, potentially allowing unauthorized database access, data exfiltration, or data manipulation.

MitigationUpgrade Frappe to version 15.106.0 or 16.16.0 or later to apply the security patch that addresses the SQL injection vulnerability in get_blog_list.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Frappe installation and version
    Run 'bench version' in the Frappe/ERPNext environment or check the/frappe/version.py file for the installed Frappe framework version
    Affected if Version is below 15.106.0 or below 16.16.0 (if using major version 16)
  2. Verify get_blog_list function exists
    Search for 'get_blog_list' in the Frappe source code, typically in modules like website.doctype.blog.blog or controllers, using 'bench execute frappe.utils.pdf.get_pdf' or grep through the bench/apps directory
    Affected if The function exists in the codebase and the installed version is vulnerable
  3. Check if blog module is enabled
    Log into Frappe/ERPNext as administrator and verify if the Blog module is installed and active via 'Modules > Website > Blog' or by querying frappe.db.get_value('DocType', 'Blog Post', 'name')
    Affected if Blog module is active and accessible via the web interface
  4. Confirm web endpoint exposure
    Access the blog list endpoint (typically /blog or /api/method/website.doctype.blog.blog.get_blog_list) via HTTP request to verify the function is exposed
    Affected if The get_blog_list function is accessible without authentication or via an authenticated but vulnerable code path

You are affected if your Frappe framework version is below 15.106.0 or below 16.16.0 AND the Blog module is enabled and accessible, allowing potential SQL injection via the get_blog_list function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Frappe to version 15.106.0 or 16.16.0 or later to apply the security patch that addresses the SQL injection vulnerability in get_blog_list.

Recommended fix High confidence

Frappe version 15.106.0 or 16.16.0 (depending on your major version branch)

  1. 1. Identify the current Frappe version running in your environment using `bench version` or checking the instance info
  2. 2. If running version 15.x: Upgrade to version 15.106.0 or later using `bench switch-to-branch version-15` or `bench update --upgrade`
  3. 3. If running version 16.x: Upgrade to version 16.16.0 or later using `bench switch-to-branch version-16` or `bench update --upgrade`
  4. 4. After upgrading, verify the fix is applied by confirming the patched get_blog_list function no longer accepts unsanitized input
  5. 5. Test the blog listing functionality to ensure normal operation
  6. 6. Review release notes for any additional security fixes included in the release
Caveat Review release notes for minor breaking changes; patch releases typically contain only bug fixes and security patches

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41581 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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