Skip to main content
Mallory
MediumVulnerability

CVE-2026-25100: Stored XSS in Bludit image upload via malicious SVG

Published Mar 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.8Medium · v4
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Bludit
IdentifiersCVE-2026-25100CWE-79 · Improper Neutralization of Input…

CVE-2026-25100 is a stored cross-site scripting vulnerability in Bludit's image upload functionality. An authenticated user with content upload privileges, including roles such as Author, Editor, or Administrator, can upload an SVG image containing attacker-controlled script payloads. Because the uploaded resource is then served and accessible without authentication, the malicious script executes in a victim's browser when the victim visits the URL of the uploaded SVG resource. Based on the provided information, all Bludit versions up to and including 3.18.2 are considered vulnerable, and CERT Polska noted that future versions might also remain vulnerable because vendor coordination stopped before a confirmed fix was documented.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated low-privilege or mid-privilege content contributor to achieve stored XSS against users who access the uploaded SVG resource. This can enable session theft, execution of arbitrary JavaScript in the victim's browser within the application's web context, unauthorized actions on behalf of the victim, credential or token capture, phishing or content injection, and potential administrative compromise if a privileged user is targeted.

Mitigation

If you can’t patch tonight, do this now.

Until a verified fix is available, disable SVG uploads entirely or restrict uploads to non-scriptable image formats. Limit upload capability to only fully trusted users, isolate user-uploaded content on a separate domain or origin, enforce restrictive Content Security Policy where feasible, and configure responses for uploaded files to reduce browser-side script execution risk. Monitoring for previously uploaded SVG files and removing untrusted content is also advisable.

Remediation

Patch, then assume compromise.

Upgrade to a vendor version that explicitly fixes CVE-2026-25100 once available. The provided content does not identify a confirmed fixed version for this CVE. Remediation should include disallowing active content in uploaded image formats, especially SVG, sanitizing SVG content server-side, validating MIME type and file content rather than extension alone, and serving user-uploaded files with headers and storage patterns that prevent script execution in the application origin.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BluditBluditapplication
FAQ

Frequently asked questions

Is CVE-2026-25100 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-25100 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25100?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-25100.
Is there a patch for CVE-2026-25100?
Upgrade to a vendor version that explicitly fixes CVE-2026-25100 once available. The provided content does not identify a confirmed fixed version for this CVE.
What products are affected by CVE-2026-25100?
Bludit.
How severe is CVE-2026-25100?
CVE-2026-25100 has a CVSS v4 score of 4.8 (Medium) and an EPSS score of 0.20% (10th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.