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

CVE-2026-44205

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 version 15.106.0, a stored XSS vulnerability in the user profile image section allows an attacker to execute malicious scripts in the browsers of other users. This issue has been patched in version 15.106.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 confidence

A stored XSS vulnerability in Frappe framework's user profile image section allows attackers to inject malicious scripts that execute in the browsers of other users viewing the infected profile. The attacker stores the malicious payload through the profile image upload/display functionality, and it executes when other users access the profile.

MitigationUpgrade Frappe to version 15.106.0 or later to apply the security patch. Alternatively, disable or restrict profile image uploads until the upgrade can be performed.

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. Identify Frappe framework installation
    Locate Frappe by checking for 'frappe' in application metadata, dependencies, or installation directories. Common locations include the Python environment site-packages or the application's composer/package.json files.
    Affected if Frappe framework is not present in the environment
  2. Determine installed Frappe version
    Run 'bench version' command in the Frappe bench directory, or check version.py/version.txt in the Frappe installation path, or inspect the requirements.txt file for the frappe version entry.
    Affected if The installed version is lower than 15.106.0 (e.g., 15.105.0, 15.x.y where y < 106)
  3. Verify profile image upload feature is accessible
    Log into the Frappe/ERPNext system as a regular user, navigate to the user profile settings, and confirm the profile image upload/change functionality is available and not disabled by system administrator.
    Affected if The profile image upload feature is enabled and accessible to users
  4. Inspect user profile data for suspicious content
    Query the database table for user records (typically 'tabUser' table) and examine the 'user_image' or 'profile_image' field for HTML/script tags, encoded payloads, or unusual URLs that may indicate stored XSS content.
    Affected if Any user record contains script tags, javascript: URLs, or other XSS payloads in the profile image field

A user is affected if Frappe version is below 15.106.0 AND the profile image upload feature is enabled and accessible in their installation.

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.106.0 or later to apply the security patch. Alternatively, disable or restrict profile image uploads until the upgrade can be performed.

Recommended fix High confidence

15.106.0

  1. 1. Back up your current Frappe installation and database before proceeding with any upgrade.
  2. 2. Update your Frappe installation to version 15.106.0 or later using your package manager or by pulling the latest code from the Frappe repository.
  3. 3. Run the necessary database migrations after the code update using the bench migrate command.
  4. 4. Clear any cached assets using bench clear-cache or bench build --clear.
  5. 5. Verify the upgrade was successful by logging in and checking that the user profile image functionality works correctly.
  6. 6. Test that the XSS vulnerability in the user profile image section is no longer exploitable.

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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