dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-44207

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, an IDOR vulnerability allows authenticated users to access other users' email configuration details. 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 · high confidence

Frappe framework prior to versions 15.107.0 and 16.17.0 contains an IDOR vulnerability where authenticated users can access other users' email configuration details by manipulating object references in API requests, bypassing proper authorization checks.

MitigationUpgrade Frappe to version 15.107.0 or 16.17.0 or later to patch the IDOR vulnerability in email configuration access controls.

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 installed Frappe version
    Run 'bench version' command or check the version file in your Frappe installation directory
    Affected if The version listed is below 15.107.0 or below 16.17.0 (if on major version 16)
  2. Confirm API access to email configuration exists
    Review API endpoints under /api/method for email-related functions (such as email_account, get_email_settings, or similar)
    Affected if Email configuration API endpoints are present and accessible to authenticated users
  3. Verify user email data is reachable via IDOR
    As an authenticated user, attempt to access email configuration data belonging to a different user by manipulating object reference parameters in API requests (such as user ID or email account ID)
    Affected if The API returns email configuration details for other users without proper ownership validation

You are affected if your Frappe installation version is below 15.107.0 or below 16.17.0 AND the email configuration API endpoints are accessible to authenticated users without proper authorization checks.

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 patch the IDOR vulnerability in email configuration access controls.

Recommended fix High confidence

Frappe v15.107.0 or v16.17.0 (depending on your major version branch)

  1. Identify the currently running Frappe version using `bench version` or checking the instance
  2. For Frappe version 15.x: Upgrade to version 15.107.0 or later by running `bench update --upgrade`
  3. For Frappe version 16.x: Upgrade to version 16.17.0 or later by running `bench update --upgrade`
  4. After upgrade, verify the patch was applied by checking release notes or running `bench version`
  5. Test that email configuration access controls work correctly - users should only be able to access their own email settings

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 / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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