FrappeApplication

CVE-2024-24812

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 14.59.0 / 15.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 that uses Python and MariaDB on the server side and a tightly integrated client side library. Prior to versions 14.59.0 and 15.5.0, portal pages are susceptible to Cross-Site Scripting (XSS) which can be used to inject malicious JS code if user clicks on a malicious link. This vulnerability has been patched in versions 14.59.0 and 15.5.0. No known workarounds are available.

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 confidence

Frappe web application framework contains a Cross-Site Scripting (XSS) vulnerability in portal pages in versions prior to 14.59.0 and 15.5.0. Attackers can craft malicious links that, when clicked by users, execute arbitrary JavaScript code in the victim's browser session.

MitigationUpgrade Frappe to version 14.59.0 or 15.5.0 to patch the XSS vulnerability. No workarounds are available.

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
FrappeApplication
Affected:< 14.59.0>= 15.0.0, < 15.5.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Frappe installation
    Run 'bench version' in the Frappe bench directory, or check the 'frappe' Python package version using 'pip show frappe'
    Affected if Frappe is not installed or cannot be determined
  2. Determine installed Frappe version
    Run 'bench version' or check the version file in your Frappe installation (typically in the sites directory or via Frappe's built-in version check)
    Affected if Installed version is below 14.59.0 or is 15.x but below 15.5.0
  3. Verify portal pages are accessible
    Check if the portal feature is enabled by navigating to any /app/portal or /web page endpoint, or by checking the Portal Settings in Frappe (accessible via: Setup > Portal Settings)
    Affected if Portal pages are enabled and accessible to users
  4. Confirm web framework handling
    Review server logs or browser developer console for any reflected URL parameters in portal pages that might be vulnerable to script injection
    Affected if URL parameters are reflected in portal page content without proper sanitization

A user is affected if they are running Frappe versions below 14.59.0 or between 15.0.0 and 15.5.0 (exclusive), and the portal feature is enabled allowing external users to access portal pages.

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
Upgrade available Upgrade to 14.59.0 / 15.5.0 or later
Fixed in 14.59.015.5.0
Interim mitigation

Upgrade Frappe to version 14.59.0 or 15.5.0 to patch the XSS vulnerability. No workarounds are available.

Recommended fix High confidence

14.59.0 (for 14.x line) or 15.5.0 (for 15.x line)

  1. Identify the current Frappe version in use (e.g., via bench version or version.py)
  2. If running Frappe version 14.x: upgrade to version 14.59.0
  3. If running Frappe version 15.x: upgrade to version 15.5.0
  4. Run database migrations after upgrade using: bench migrate
  5. Clear cache: bench clear-cache
  6. Verify the upgrade was successful and test portal functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Frappe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24812 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24812 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