Loading vulnerability…
CVE-2026-44175 is a persistent cross-site scripting vulnerability in the Kirby content management system affecting versions prior to 4.9.1 and 5.x versions prior to 5.4.1. The flaw exists because Kirby's list field stores formatted content as HTML, but server-side sanitization was not performed when that content was saved. Sanitization was enforced only in the Panel client, allowing an attacker to bypass the normal editing interface and submit malicious HTML directly to the backend API. The unsanitized markup could then be written into content files and later rendered by the site frontend. When rendered, the attacker-controlled markup executes in the browsers of site visitors and authenticated users, resulting in stored XSS. The issue affects sites that use the list field or list block and permit content updates by users who are not fully trusted.
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.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.