CVE-2026-31879
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 14.100.2, 15.101.0, and 16.10.0, due to a lack of validation and improper permission checks, users could modify other user's private workspaces. Specially crafted requests could lead to stored XSS here. This vulnerability is fixed in 14.100.2, 15.101.0, and 16.10.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 confidenceAn insecure direct object reference (IDOR) vulnerability in Frappe framework allows authenticated users to modify other users' private workspace configurations due to missing permission validation. The lack of proper authorization checks on workspace modification endpoints, combined with the ability to inject malicious scripts through crafted requests, results in stored cross-site scripting (XSS).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 14.100.2>= 15.0.0, < 15.101.0>= 16.0.0, < 16.10.0CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 your Frappe/ERPNext installation directory, or check the version in your sites/[sitename]/site_config.json file under 'frappe_version' or inspect the version module via Python: 'bench execute frappe.utils.get_fullname' or check the installed version from requirements.txtAffected if The installed version is < 14.100.2, OR >= 15.0.0 and < 15.101.0, OR >= 16.0.0 and < 16.10.0
-
Verify workspace module is enabledLog in as an authenticated user and navigate to the workspace settings, or check via API: GET /api/method/frappe.desk.desktop.get_workspace_by_name with a valid user sessionAffected if The workspace module is active and users have access to create or modify private workspaces
-
Test workspace modification endpoint for IDORAs User A, create a private workspace and capture the workspace name/ID. Then as User B, attempt a PUT or POST request to /api/method/frappe.desk.page.workspace.workspace.set_custom_css or /api/method/frappe.desk.page.workspace.workspace.save_workspace to modify User A's workspace using the captured workspace nameAffected if User B can successfully modify User A's private workspace configuration without receiving a 403 Forbidden or permission error
-
Inspect for stored XSS in workspace contentCheck the workspace document in the database table 'Workspace' (or DocType 'Workspace') for any script tags or malicious content in fields like 'content', 'script', 'on_load', or 'custom_scripts' that were not created by the workspace ownerAffected if Workspace documents contain unsanitized script tags or XSS payloads that were injected by another user
-
Review API permission logsCheck server logs orbench output for requests to workspace modification endpoints. Look for successful responses (200 OK) where the requesting user differs from the workspace ownerAffected if Logs show authenticated users successfully modifying workspaces owned by different users without authorization errors
You are affected if your Frappe version falls within the vulnerable ranges AND users can modify other users' private workspace configurations through the API without permission errors.
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 · scoped14.100.215.101.016.10.0
Upgrade to Frappe versions 14.100.2, 15.101.0, or 16.10.0 which implement proper permission validation on workspace modification endpoints and sanitize user inputs.
14.100.2 (for v14.x), 15.101.0 (for v15.x), or 16.10.0 (for v16.x)
- 1. Identify the current Frappe version by checking the installed version in your environment
- 2. Determine which major version branch (14.x, 15.x, or 16.x) you are currently running
- 3. For version 14.x: Upgrade to version 14.100.2 or later
- 4. For version 15.x: Upgrade to version 15.101.0 or later
- 5. For version 16.x: Upgrade to version 16.10.0 or later
- 6. After upgrading, verify the fix is applied by checking that users cannot modify other users' private workspaces
- 7. Test that stored XSS payloads in workspace configurations are properly sanitized and not executable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31879 — 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-31879 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