Quick answers
- Is CVE-2026-81927 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81927 being exploited in the wild.
- How severe is CVE-2026-81927?
- Medium severity, with a CVSS score of 5.4, published 15 September 2026.
- Which products and versions are affected?
- Concrete CMS before 9.5.3.
- Is there a fix for CVE-2026-81927?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81927 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81927?
- Check whether you run Concrete CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored XSS flaw in SVG file handling when the svg_sanitization.action is set to "reject" mode. The vulnerability exists because the sanitization logic only checks against a small built-in blocklist (script element and on* event handlers) but discards the results of the broader enshrined/svg-sanitize library, allowing vectors like javascript: URIs in xlink:href attributes to pass through unstripped. An authenticated user with file upload privileges can upload a malicious SVG file containing JavaScript code, which will execute in the browser context of any user who directly opens the file. The default "sanitize" mode is not affected. A patch is available in Concrete CMS version 9.5.3 and later.
Affected products
- Concrete CMS Concrete CMS before 9.5.3
Timeline
- 2026-09-15: disclosed