dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-44976

MEDIUM · 5.3 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 →
59/100
Remediation priority · Elevated
Remotely reachable 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 version 16.17.4, any user can modify any field in any Onboarding Step record. This issue has been patched in version 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 · high confidence

Frappe framework versions prior to 16.17.4 contain an Insecure Direct Object Reference (IDOR) vulnerability where any authenticated user can modify fields in any Onboarding Step record without proper authorization checks, allowing unauthorized data manipulation across the system.

MitigationUpgrade Frappe to version 16.17.4 or later which includes proper authorization validation for Onboarding Step field modifications.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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 framework version
    Run 'bench version' in the Frappe bench directory or inspect the version file in your Frappe installation
    Affected if The installed version is below 16.17.4 (e.g., 16.17.3, 16.16.0, etc.)
  2. Confirm Onboarding module is present
    Check if the Onboarding module exists in your Frappe instance by accessing the modules list or running 'bench list-apps' to see if core apps including onboarding are installed
    Affected if The Onboarding module is installed and accessible in the system
  3. Verify user authentication is enabled
    Confirm that the Frappe site has user authentication configured by checking if the '/api/method/...' endpoints require login
    Affected if Any authenticated user account exists in the system (the vulnerability affects any authenticated user, not just administrators)
  4. Check for Onboarding Step records
    Navigate to the Onboarding Step doctype in Frappe (usually at /app/onboarding-step) or query the database table for records in the Onboarding Step document type
    Affected if There are Onboarding Step records defined in the system that could be modified

You are affected if Frappe version is below 16.17.4 AND the Onboarding module with Onboarding Step records exists in your environment, since any authenticated user can modify those records without authorization.

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 16.17.4 or later which includes proper authorization validation for Onboarding Step field modifications.

Recommended fix High confidence

16.17.4

  1. Upgrade Frappe framework to version 16.17.4 or later

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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