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

CVE-2026-53568

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.2 and 16.17.4, there is a stored XSS vulnerablity in Frappe Report/List View. This issue has been patched in versions 15.107.2 and 16.17.4.

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 stored Cross-Site Scripting (XSS) vulnerability exists in Frappe's Report/List View component. The vulnerability allows malicious JavaScript to be persisted in the database and executed when other users access the affected report or list views. This is a medium-severity issue (CVSS 6.9) affecting Frappe framework versions prior to 15.107.2 and 16.17.4.

MitigationUpgrade Frappe to version 15.107.2 or 16.17.4 or later. Additionally, implement output encoding and Content Security Policy headers as defense-in-depth measures.

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 installation
    Identify whether the Frappe framework is present in your environment. This may involve checking for Frappe-specific directories, running processes (bench), or the presence of frappe libraries in your Python environment.
    Affected if Frappe framework is installed and running
  2. Determine installed Frappe version
    Run the command to retrieve the Frappe version. Typically this can be done via: 1) Check the installed frappe package version with 'pip show frappe' or 'bench version', 2) Inspect the version file in the Frappe bench directory, or 3) Query the site database for the installed Frappe version.
    Affected if The installed version is lower than 15.107.2 OR lower than 16.17.4 (for the respective major version branch)
  3. Identify active Report and List Views
    Examine the Frappe instance for any custom reports or list views that accept user input. This can be done by: 1) Reviewing custom reports in the Report Builder, 2) Checking custom DocTypes with list views that may contain user-submitted data, or 3) Querying the database for records in Report and List View related tables.
    Affected if Custom reports or list views exist that could accept and store unsanitized user input
  4. Verify database for suspicious script content
    Search the database tables associated with reports and list views for stored JavaScript or script tags. Query tables that store report configurations, list view filters, or custom field values for patterns like '<script', 'javascript:', or event handlers (onload, onerror, etc.).
    Affected if Any records contain executable JavaScript or HTML/script content that was not properly escaped

You are affected if your Frappe installation version is below 15.107.2 (for version 15.x) or below 16.17.4 (for version 16.x) AND your instance has custom reports or list views that could store unsanitized user input.

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.2 or 16.17.4 or later. Additionally, implement output encoding and Content Security Policy headers as defense-in-depth measures.

Recommended fix High confidence

Frappe version 15.107.2 or 16.17.4

  1. Identify the current Frappe version by checking the installation or frappe --version command
  2. Review the Frappe release notes for versions 15.107.2 and 16.17.4 to understand changes
  3. Create a backup of the current Frappe installation and database
  4. Upgrade Frappe to version 15.107.2 (for the 15.x branch) or 16.17.4 (for the 16.x branch) using the standard Frappe upgrade process
  5. Verify the upgrade was successful by checking the new version
  6. Test the Report/List View functionality to confirm the XSS vulnerability is resolved
Caveat Review release notes for any breaking changes between current version and target version

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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