dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-50701

MEDIUM · 5.1 CVSS v4.0 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A Reflected Cross-Site Scripting (XSS) vulnerability exists in Frappe Framework version 17.0.0-dev due to improper neutralization of user-controlled input in the dashboard-view component.

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

A reflected XSS vulnerability exists in Frappe Framework version 17.0.0-dev within the dashboard-view component. User-controlled input is improperly neutralized, allowing malicious scripts to be injected and executed in the context of other users' browsers when they access the crafted URL.

MitigationImplement proper input validation and output encoding/escaping in the dashboard-view component to ensure user-supplied data is safely rendered without executing as JavaScript.

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
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/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 if Frappe Framework is in use
    Check your application's tech stack or look for Frappe-related files, processes, or services running in your environment
    Affected if Frappe Framework is not present - you are not affected by this CVE
  2. Check Frappe Framework version
    Locate the Frappe installation and determine the exact version number, typically found in version files, package.json, or via frappe --version CLI command
    Affected if The installed version is 17.0.0-dev - you are directly affected; versions other than 17.0.0-dev are not affected by this specific vulnerability
  3. Determine if dashboard-view component is enabled
    Check if the dashboard-view component is accessible or enabled in your Frappe instance configuration or routing setup
    Affected if Dashboard-view is not in use or disabled - the attack surface may not be accessible even if on the affected version
  4. Inspect URL handling in dashboard-view
    Examine how the dashboard-view component processes URL parameters and user input - look for any parameters that get rendered back into the page without encoding
    Affected if User-supplied parameters in the URL are reflected in the dashboard-view output without proper escaping - you are vulnerable to reflected XSS

You are affected only if you have Frappe Framework version 17.0.0-dev with the dashboard-view component enabled and accessible, where URL parameters are reflected without proper encoding.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/escaping in the dashboard-view component to ensure user-supplied data is safely rendered without executing as JavaScript.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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