CVE-2026-47422
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 · uneditedFrappe is a full-stack web application framework. Prior to 15.107.5 and 16.18.2, an endpoint in reportview lacked appropriate permission checks and that has since been fixed. This vulnerability is fixed in 15.107.5 and 16.18.2.
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 confidenceFrappe framework versions prior to 15.107.5 and 16.18.2 contain an authorization bypass vulnerability in the reportview endpoint where permission checks were not properly enforced, potentially allowing unauthorized access to report data.
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:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Frappe versionRun 'bench version' in the Frappe bench directory, or check the version file in the Frappe installation (frappe/__init__.py typically contains the version string)Affected if Version is below 15.107.5 for the 15.x branch or below 16.18.2 for the 16.x branch
-
Confirm Frappe major version branchLook at the first number in the version (e.g., 15.x.x or 16.x.x) to determine which branch is runningAffected if Running version 15.x below 15.107.5, or version 16.x below 16.18.2
-
Verify reportview endpoint is accessibleAttempt a GET request to a reportview endpoint (typically /api/method/frappe.boot) or check if any report functionality is exposed via APIAffected if The reportview API endpoint responds and returns data without proper authorization headers or session cookies
-
Test authorization on reportview endpointMake an unauthenticated or low-privilege API request to a reportview resource and observe if data is returned without a 403 Forbidden responseAffected if Unauthenticated or unauthorized users can retrieve report data through the reportview endpoint
Environment is affected if running Frappe version 15.x below 15.107.5 or version 16.x below 16.18.2 AND the reportview API endpoint is accessible and returns data without proper permission enforcement.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Frappe installations to version 15.107.5 or 16.18.2 or later to apply the permission check fix.
15.107.5 or 16.18.2 (depending on major version in use)
- Identify the current Frappe version in use (either 15.x or 16.x branch)
- If using Frappe version 15.x, upgrade to version 15.107.5
- If using Frappe version 16.x, upgrade to version 16.18.2
- After upgrade, verify the reportview endpoint now includes proper permission checks
- Test that existing report functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47422 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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