Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain upload-capable account
-
DeliveryUpload crafted malicious SVG
-
ExploitLure victim to raw SVG URL
-
ExecutionBrowser executes embedded script
-
ImpactHijack session or act in site origin
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) an authenticated Backdrop CMS account with permission to upload SVG images (PR:L), and (2) a victim who opens the uploaded SVG directly via its raw file URL rather than viewing it on a normal page. The key limiting factor is Backdrop's design of embedding all uploaded SVGs within <img> tags, which blocks script execution in ordinary rendering - so a victim must be induced to navigate straight to the SVG's URL for any embedded scripting to run. Affected only on Backdrop CMS Core 1.35.x before 1.35.2 and 1.34.x before 1.34.6; it is not remote-unauthenticated against default configurations because the upload privilege and the direct-URL viewing step are both prerequisites. |
| Impact | This is a moderate-severity stored cross-site scripting (CWE-79) issue in Backdrop CMS core, and the available signals converge on genuinely limited real-world risk rather than an urgent priority. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N, base 5.3) indicates network reachability with low attack complexity but requires authenticated privileges (PR:L) - specifically an account permitted to upload files/images. There is no EPSS score provided, no CISA KEV listing, and no public POC referenced, so exploitation status is: no public exploit identified at time of analysis. Two strong mitigating factors cut against the headline CVSS: Backdrop embeds uploaded SVGs inside <img> tags, which does not execute embedded script, so the attacker's payload only runs if a victim manually navigates directly to the raw SVG file URL. The CVSS vector marks VC:N (no confidentiality impact) and UI:N, but these appear understated/inconsistent for a reflected-in-browser XSS: script execution in a victim's authenticated session can plausibly expose session data (arguing C:L) and realistically requires a victim to open the SVG URL (arguing user interaction) - verify these metric choices with the vendor advisory. Net assessment: a real but low-to-moderate bug gated behind both an upload-capable account and an unusual victim action (direct URL viewing), making opportunistic mass exploitation unlikely. |
| Exploit ScenarioDerived | An authenticated user with permission to upload images uploads a crafted SVG containing embedded JavaScript or a clickable link. Because Backdrop renders SVGs inside <img> tags, the script stays dormant on normal pages; the attacker then lures a victim (e.g., an administrator) into opening the raw SVG file by its direct URL, at which point the browser executes the embedded script in the site's origin. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Stored cross-site scripting in Backdrop CMS Core 1.35.x before 1.35.2 and 1.34.x before 1.34.6 allows an authenticated user holding SVG upload permission to embed dangerous tags or scripting inside an uploaded SVG image, which will execute in a victim's browser only if that SVG is opened directly by its raw file URL. Backdrop's design of embedding all uploaded SVGs inside <img> tags blocks that script during normal page rendering, and reaching the payload requires both the upload privilege (PR:L per the assessed vector) and a victim who navigates to the file itself, so this is a moderate-severity issue (CVSS 5.3, CWE-79) with no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
RemediationAI
Apply the vendor-released patches by upgrading to Backdrop CMS Core 1.35.2 if the site runs the 1.35.x branch, or to 1.34.6 if it runs the 1.34.x branch (see https://backdropcms.org/security/backdrop-sa-core-2026-007 for the full advisory). If upgrading cannot be done immediately, the most direct compensating control is to restrict the SVG upload permission to a small set of fully trusted roles, or to remove image/svg+xml from the set of allowed upload extensions if legitimate vector graphics are not required - the trade-off being that editors lose SVG support. Alternatively, serve the files directory (or at minimum stored uploads) from a separate origin, or attach Content-Disposition: attachment and a restrictive Content-Security-Policy such as script-src 'none' or a sandbox directive to uploaded SVG responses, which neutralizes any stored payload even before patching at the cost of additional web-server configuration and possible breakage of legitimate inline image behavior. Because Backdrop embeds uploaded SVGs in <img> tags by default, residual risk is concentrated in scenarios where users can be lured into opening a file's raw URL directly.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Backdrop CMS is a Drupal-derived content management system whose media handling accepts SVG (Scalable Vector Graphics) uploads. Because SVG is an XML format, an uploaded file can legitimately carry <script> elements, onload/onclick event handlers, and javascript: links, making it effectively an HTML document with an image MIME type. CWE-79 (Improper Neutralization of Input During Web Page Generation) is the root-cause class here: core did not sufficiently validate uploaded SVGs to reject or strip those dangerous tags before storage and serving. CPE cpe:2.3:a:backdropcms:backdrop:*:*:*:*:*:*:*:* identifies the Backdrop CMS product line as a whole; the vulnerable branches are 1.35.x prior to 1.35.2 and 1.34.x prior to 1.34.6. Two design factors bound the real-world impact and explain the assessed vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N): the SVG upload capability is gated behind an authenticated account with the relevant permission, and Backdrop renders stored SVGs inside <img> tags, where browsers do not execute embedded script. Payload execution therefore depends on the victim being induced to browse the raw file URL directly rather than viewing the image on a normal page.
Know when Backdrop gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N
Requires an upload-capable account (PR:L) and a victim viewing the raw SVG URL (UI:R); script runs in the site origin (S:C) enabling limited session/DOM impact (C:L/I:L).
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
1DescriptionCVE.org
Backdrop CMS Core 1.35.x before 1.35.2 and 1.34.x before 1.34.6 does not sufficiently validate uploaded SVG images to ensure they lack potentially dangerous SVG tags. SVG images can contain clickable links or executable scripting. By uploading a crafted SVG, it is possible to execute scripting in the browser when an SVG image is viewed. This issue is mitigated by the attacker needing to be able to upload SVG images, and that Backdrop embeds all uploaded SVG images within <img> tags, which prevents script from executing. The SVG must be viewed directly by its URL in order to run any embedded scripting.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) becaus
Backdrop CMS version 1.23.0 was discovered to contain a stored cross-site scripting (XSS) vulnerability via 'Comment.' .
Backdrop CMS version 1.23.0 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the 'Card' c
Information disclosure in Backdrop CMS 1.34.x before 1.34.5 and 1.35.x before 1.35.1 allows remote unauthenticated attac
Information disclosure in Backdrop CMS Core's token browser allows authenticated users to enumerate available token type
Backdrop CMS 1.12.x before 1.12.8 and 1.13.x before 1.13.3 doesn't sufficiently filter output when displaying certain bl
Backdrop CMS before 1.27.3 and 1.28.x before 1.28.2 does not sufficiently sanitize field labels before they are displaye
EUVD-2026-102595
GHSA-gcjx-3jpq-qx2p
NVD
CVE.org
EPSS
Exploit-DB