Loading vulnerability…
TypiCMS (Laravel-based CMS) Core prior to 16.1.7 contains a stored cross-site scripting vulnerability in its file upload module. Users with file upload permissions can upload SVG files that pass MIME-type validation, but the SVG content is not sanitized. An attacker can embed malicious JavaScript (e.g., via script elements and/or event handlers) in a crafted SVG; when another user (notably an administrator) views or accesses the uploaded SVG through the application, the attacker-controlled script executes in the victim’s browser context. A related SVG parsing bug may trigger a 500 error when an uploaded SVG lacks a viewBox attribute, but this does not prevent exploitation because a malicious SVG can include a valid viewBox. The issue is fixed in TypiCMS Core 16.1.7.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
TypiCMS\Modules\Core\Http\Requests\FileFormRequest.php). (2) If SVG support is required, sanitize SVGs on upload using a dedicated SVG sanitization library to remove scripts, foreignObject, inline styles, and on* event handlers. (3) Deploy a strict Content-Security-Policy to block inline script execution. (4) Serve user-uploaded content from a separate, cookie-less domain/origin to isolate untrusted uploads from the main application origin.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.