dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-44975

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 versions 15.107.2 and 16.17.4, any authenticated user can reset onboarding for all users in the system. 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 · high confidence

Frappe framework prior to versions 15.107.2 and 16.17.4 lacks proper authorization checks on the onboarding reset endpoint, allowing any authenticated user to reset onboarding status for all users in the system.

MitigationUpgrade Frappe to version 15.107.2 or 16.17.4 or later. Verify that non-admin users can no longer trigger bulk onboarding resets.

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 installed Frappe version
    Access the Frappe desk, go to Help > About, or run 'bench version' from the command line to retrieve the exact version number
    Affected if Version is below 15.107.2 or below 16.17.4 (or between 15.x and 15.107.2, or between 16.x and 16.17.4)
  2. Confirm user role in the system
    Log in as a non-administrator user and navigate to the user profile or run 'bench show-user' to verify the role is not Administrator
    Affected if The test account has a role other than Administrator (e.g., Employee, Customer, or any custom non-admin role)
  3. Inspect onboarding reset endpoint permissions
    Locate the onboarding reset API endpoint in the Frappe source (typically in /api/ method handling onboarding reset) and review the permission manager settings or the @whitelist decorator to verify if authorization is enforced
    Affected if The endpoint lacks a permission check (e.g., @requires_guest or no @permissions decorator) or allows 'All' roles to execute it
  4. Test endpoint behavior with non-admin account
    Using a non-admin user session, make a request to the onboarding reset endpoint (e.g., via browser developer tools or curl to /api/method/frappe.utils.reset_onboarding) and observe whether the request succeeds
    Affected if The request completes successfully and returns a 200 OK response instead of 403 Forbidden

You are affected if your Frappe version is below 15.107.2 or below 16.17.4 AND the onboarding reset endpoint permits non-administrator users to reset onboarding status for all users in the system.

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. Verify that non-admin users can no longer trigger bulk onboarding resets.

Recommended fix High confidence

Frappe version 15.107.2 or later (for 15.x branches); Frappe version 16.17.4 or later (for 16.x branches)

  1. Identify the currently installed Frappe version by checking the application's version information
  2. If running Frappe version 15.x, upgrade to version 15.107.2 or later
  3. If running Frappe version 16.x, upgrade to version 16.17.4 or later
  4. Verify the upgrade was successful by checking the new version number
  5. Test that the onboarding reset functionality now properly enforces authorization checks
  6. Deploy the updated version to production

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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