dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-44208

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, lack of validations in the "submit_discussion()" endpoint allows for 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 framework's submit_discussion() endpoint lacks proper validation checks, allowing authenticated users to access resources they shouldn't have permission to access. This is an Insecure Direct Object Reference (IDOR) or broken access control vulnerability where the endpoint fails to verify user permissions before processing discussion submissions.

MitigationUpgrade Frappe to version 15.107.0 or 16.17.0 or later, which includes proper authorization validations in the submit_discussion() endpoint.

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: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. Confirm Frappe framework is in use
    Look for frappe installation directory (commonly bench/sites or frappe-bench), or check Python packages with 'pip list | grep -i frappe'
    Affected if Frappe framework is not installed on the system
  2. Identify installed Frappe version
    Run 'bench version' from the frappe-bench directory, or check version file at apps/frappe/frappe/__init__.py, or query the database table 'tabDefaultValue' for 'app_version'
    Affected if The installed version is unknown or cannot be determined
  3. Locate the submit_discussion endpoint
    Search the codebase for 'submit_discussion' in Python files under apps/frappe/frappe/ - typically found in controller or API modules handling discussion features
    Affected if The submit_discussion function does not exist in the codebase (already patched or not using this feature)
  4. Check for authorization validation in submit_discussion
    Examine the submit_discussion function code and look for permission checks such as 'has_permission', 'check_permission', or 'frappe.permissions' calls before processing the discussion submission
    Affected if The endpoint lacks proper permission validation checks and directly processes requests based on user-supplied parameters without authorization verification

A user is affected if they are running a Frappe version prior to 15.107.0 or 16.17.0 AND the submit_discussion endpoint exists without proper authorization validation in its code.

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, which includes proper authorization validations in the submit_discussion() endpoint.

Recommended fix High confidence

Frappe 15.107.0 or 16.17.0 (depending on your current major version branch)

  1. 1. Identify the currently installed Frappe version by checking the application's version file or deployment configuration.
  2. 2. If running Frappe version 15.x, upgrade to version 15.107.0 or later.
  3. 3. If running Frappe version 16.x, upgrade to version 16.17.0 or later.
  4. 4. For mixed deployments (both version branches), upgrade each instance to its respective patched release.
  5. 5. After upgrading, verify the submit_discussion() endpoint now properly validates authorization before allowing access to resources.
  6. 6. Test the discussion submission functionality to ensure normal operations work as expected post-upgrade.
Caveat Review release notes for any breaking changes between your current version and 15.107.0/16.17.0 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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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