dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-44206

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.107.2 and 16.17.4, DB Schema Enumeration is possible through exploiting an endpoint. This issue has been patched in versions 15.107.2 and 16.17.4.

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 · moderate confidence

Frappe framework versions prior to 15.107.2 and 16.17.4 contain an endpoint that allows unauthenticated or low-privilege attackers to enumerate database schema information, exposing table names, column structures, and potentially sensitive metadata about the application's data model.

MitigationUpgrade Frappe to version 15.107.2 or 16.17.4 or later to patch the vulnerable endpoint. If immediate upgrade is not possible, restrict network access to the affected endpoint as a temporary compensating control.

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:N/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 framework version
    Check the installed Frappe version via the command 'bench version' or by inspecting the version file in the Frappe installation directory
    Affected if Version is below 15.107.2 or 16.17.4 (or between 15.x and 16.x with version less than the patched releases)
  2. Locate the API endpoint
    Examine Frappe's API routing configuration files (typically in the frappe/api.py or frappe/app.py) to identify schema-related endpoints, particularly those handling database metadata queries
    Affected if A schema enumeration endpoint exists in the codebase and is routed without version-specific path restrictions
  3. Verify endpoint accessibility
    Attempt to access the suspected schema endpoint using a web request tool (curl, browser DevTools) without providing valid authentication credentials
    Affected if The endpoint responds with database schema data (table names, column names, table structures) without requiring authentication
  4. Check API authentication configuration
    Inspect the endpoint's authentication decorators in the Frappe source code or examine the API Gateway/WAF rules controlling access to this endpoint
    Affected if The endpoint either lacks @frappe.apikey.auth or @frappe.login_required decorators, or network-layer controls permit unauthenticated access
  5. Confirm low-privilege user access
    Log in with a low-privilege user account (e.g., a guest or standard user role) and attempt to access the endpoint
    Affected if The endpoint returns schema information to users without System Manager or Administrator privileges

You are affected if your Frappe installation version is prior to 15.107.2 or 16.17.4 AND the vulnerable schema enumeration endpoint is accessible without proper authentication.

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.107.2 or 16.17.4 or later to patch the vulnerable endpoint. If immediate upgrade is not possible, restrict network access to the affected endpoint as a temporary compensating control.

Recommended fix Moderate confidence

Frappe v15.107.2 or v16.17.4 (depending on your major version branch)

  1. Identify your current Frappe version by checking the bench or installation
  2. For Frappe version 15.x: Upgrade to version 15.107.2 or later
  3. For Frappe version 16.x: Upgrade to version 16.17.4 or later
  4. Run bench update to apply the patch
  5. Verify the upgrade was successful and the endpoint is no longer exposing schema information
  6. Test that application functionality remains intact after upgrade
Caveat Review release notes for version 15.107.2 and 16.17.4 for any potential breaking changes before upgrading

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44206 — 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-44206 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