dbcve.org
FrappeApplication

CVE-2026-28436

HIGH · 7.2 CVSS v3.1 Published 2026-03-05
Fix available
A fix is available. Upgrade to 15.102.0 / 16.11.0 or later.
See remediation →
81/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 16.11.0 and 15.102.0, an attacker can set a crafted image URL that results in XSS when the avatar is displayed, and it can be triggered for other users via website page comments. This issue has been patched in versions 16.11.0 and 15.102.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 · moderate confidence

Frappe framework versions prior to 15.102.0 and 16.11.0 contain a stored XSS vulnerability in the avatar display functionality. Attackers can set a crafted image URL containing malicious JavaScript that executes when other users view the avatar in website page comments.

MitigationUpgrade Frappe to version 15.102.0 or 16.11.0 or later to apply the security patch.

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:< 15.102.0>= 16.0.0, < 16.11.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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check installed Frappe version
    Run 'bench version' or inspect the Frappe installation directory for the version file. On Linux typically at ~/frappe-bench/sites/[site name]/site_config.json or check the version via Frappe UI at /app/about
    Affected if Version is below 15.102.0 OR version is 16.0.0 through 16.10.x
  2. Identify if avatar/profile feature is in use
    Check if users have set custom avatar images. Query the database table for user profiles (typically 'tabUser' or 'tabProfile' table) for non-default avatar values. Run: SELECT name, user_image FROM tabUser WHERE user_image IS NOT NULL AND user_image != ''
    Affected if Users exist with custom user_image values set to external URLs
  3. Inspect stored avatar URLs for malicious content
    Examine the user_image field values from the previous query. Look for URLs containing javascript: protocol, onerror= attributes, <script> tags encoded in URLs, or other XSS payloads
    Affected if Any avatar URL contains javascript: or other XSS vectors like encoded script tags, data: URIs with script content, or event handlers
  4. Check for avatar rendering in comments
    Review the comment rendering code or templates that display user avatars in website pages. Look for places where avatar URLs are rendered without sanitization. Inspect page source of comment sections to see how avatars are loaded
    Affected if Avatar images are rendered using an unsafe method (such as direct src attribute insertion without sanitization)

Environment is affected if running Frappe version below 15.102.0 or between 16.0.0 and 16.10.x AND users have set custom avatar image URLs that could contain malicious scripts.

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 15.102.0 / 16.11.0 or later
Fixed in 15.102.016.11.0
Interim mitigation

Upgrade Frappe to version 15.102.0 or 16.11.0 or later to apply the security patch.

Recommended fix High confidence

Frappe 15.102.0+ (for 15.x branch) or Frappe 16.11.0+ (for 16.x branch)

  1. Identify your current Frappe version by running 'bench version' or checking your requirements.txt
  2. If running Frappe 15.x branch: upgrade to version 15.102.0 or later using 'bench get-app frappe --version 15.102.0' or your package manager
  3. If running Frappe 16.x branch: upgrade to version 16.11.0 or later using 'bench get-app frappe --version 16.11.0' or your package manager
  4. Run 'bench migrate' after upgrading to apply database migrations
  5. Clear any application caches (bench clear-cache)
  6. Verify the upgrade was successful by checking 'bench version'
Caveat Review Frappe release notes for your specific version jump to check for any breaking changes or required migration steps

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

Fix this in Frappe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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