dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-50026

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.0 and 16.17.0, a lack of permission checks in these endpoints allowed unauthorized access to resources. This issue has been patched in versions 15.107.0 and 16.17.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 · moderate confidence

Frappe web application framework versions prior to 15.107.0 and 16.17.0 contain an Insecure Direct Object Reference (IDOR) vulnerability where certain API endpoints lack proper permission validation, allowing unauthenticated or unauthorized users to access sensitive resources they should not be able to reach.

MitigationUpgrade Frappe to version 15.107.0 or 16.17.0 or later to apply the patched permission checks. Review existing endpoint access controls after upgrading.

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 the command 'bench version' in the Frappe installation directory, or check the version file in the Frappe framework installation (typically in the 'frappe' Python package metadata).
    Affected if The installed version is less than 15.107.0 or is between 15.107.0 and 15.x.x (but less than 15.107.0) OR the installed version is less than 16.17.0 or is between 16.17.0 and 16.x.x (but less than 16.17.0).
  2. Confirm Frappe framework is actively running
    Check if the Frappe web server is running by accessing the home page of the Frappe instance or by querying the process list for Frappe-related Python processes.
    Affected if The Frappe application is actively serving requests and the version falls into the affected range from step 1.
  3. Identify exposed API endpoints
    Review the application's API routing configuration to determine which endpoints are accessible. In Frappe, this typically involves examining the 'frappe/api.py' and any custom app API routes, or by probing common API paths such as '/api/method/' or '/api/resource/'.
    Affected if API endpoints are publicly accessible without authentication or without proper permission checks applied.
  4. Test for IDOR on sensitive resource endpoints
    Attempt to access sensitive resources (such as user data, documents, or configuration endpoints) via API calls using an unauthenticated request or a request with limited permissions. Compare the HTTP response codes and data returned against what should be accessible based on the requestor's authorization level.
    Affected if The API returns sensitive data or allows actions on resources that the requesting user should not have access to, indicating missing permission validation.

The environment is affected if Frappe version is prior to 15.107.0 or prior to 16.17.0 and the API endpoints lack proper permission validation, allowing unauthorized access to sensitive resources.

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.0 or 16.17.0 or later to apply the patched permission checks. Review existing endpoint access controls after upgrading.

Recommended fix High confidence

Upgrade to Frappe version 15.107.0 (for v15 branches) or 16.17.0 (for v16 branches)

  1. Identify the current Frappe version in use by checking the deployed application
  2. For Frappe version 15.x: Upgrade to version 15.107.0 or later
  3. For Frappe version 16.x: Upgrade to version 16.17.0 or later
  4. After upgrading, verify that the permission checks are properly enforced on the affected endpoints
  5. Review application logs to confirm no unauthorized access attempts occurred prior to the upgrade
Caveat Review Frappe release notes for version 15.107.0 and 16.17.0 to check for any breaking changes that may affect custom apps or integrations

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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