PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-66059 frappe CVE debrief

A field-level permissions bypass in Frappe exposes restricted DocType fields. This issue is fixed in versions 16.23.0 and 15.112.0. The vulnerability allows unauthorized access to sensitive data, potentially leading to data breaches or system compromise. Defenders should assess their exposure and prioritize patching or mitigating this vulnerability to prevent potential unauthorized access. The CVE record and NVD entry provide details on the vulnerability and its fixes, but additional information on exploitation or specific impacts is not available.

Vendor
frappe
Product
Unknown
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-07
Original CVE updated
2026-09-08
Advisory published
2026-08-07
Advisory updated
2026-09-08

Who should care

Defenders and administrators using Frappe should assess their exposure and prioritize patching or mitigating this vulnerability to prevent potential unauthorized access. This includes verifying Frappe versions, applying patches or updates to affected systems, and monitoring system logs for suspicious activity. Security teams should review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

A field-level permissions bypass in Frappe exposes restricted DocType fields, requiring defenders to verify exposure and prioritize patching or mitigation.

  • Verify exposure and assess impact on systems using Frappe versions prior to 16.20.0 and 15.112.0
  • Prioritize patching or mitigating this vulnerability to prevent potential unauthorized access

Technical summary

Frappe versions prior to 16.20.0 and 15.112.0 are vulnerable to a field-level permissions bypass, exposing restricted DocType fields. This vulnerability allows unauthorized access to sensitive data, potentially leading to data breaches or system compromise. The issue is fixed in versions 16.23.0 and 15.112.0. Defenders should assess their exposure and prioritize patching or mitigating this vulnerability to prevent potential unauthorized access. The CVE record and NVD entry provide details on the vulnerability and its fixes.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those using Frappe versions prior to 16.20.0 and 15.112.0.

Recommended defensive actions

  • Verify Frappe version and assess exposure
  • Apply patches or updates to affected systems
  • Monitor system logs for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability and its fixes. However, additional information on exploitation or specific impacts is not available. Defenders should verify Frappe versions and assess exposure to this vulnerability. The vulnerability is fixed in versions 16.23.0 and 15.112.0. There is no evidence of exploitation in the wild, but defenders should still prioritize patching or mitigation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-66059 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-66059

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-66059 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66059

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.