CVE-2026-81927
Last modified
CVE-2026-81927 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. Concrete CMS before 9.5.3 contained a stored cross-site scripting vulnerability in SVG file handling. When SVG processing was set to the non-default "Reject files containing potentially harmful elements" mode (concrete.file_manager.images.svg_sanitization.action = reject), uploaded SVGs were checked only against a small built-in blocklist covering the script element and on* event-handler attributes; the broader enshrined/svg-sanitize pass still ran, but its result was discarded, so vectors it would have stripped, such as a javascript: URI in an xlink:href, were stored unmodified and executed when the file was opened directly. EPSS estimates a 0.31% chance of exploitation in the next 30 days.
Description
Concrete CMS before 9.5.3 contained a stored cross-site scripting vulnerability in SVG file handling. When SVG processing was set to the non-default "Reject files containing potentially harmful elements" mode (concrete.file_manager.images.svg_sanitization.action = reject), uploaded SVGs were checked only against a small built-in blocklist covering the script element and on* event-handler attributes; the broader enshrined/svg-sanitize pass still ran, but its result was discarded, so vectors it would have stripped, such as a javascript: URI in an xlink:href, were stored unmodified and executed when the file was opened directly. A user able to upload files could thereby run arbitrary JavaScript in the browser of any user who viewed the file. The default sanitize mode was not affected. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 1.8 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Oriol Ortiz for reporting.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Concretecms | Concrete Cms | < 9.5.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-81927?
How severe is CVE-2026-81927?
How do I fix CVE-2026-81927?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-81921Concrete CMS 8.5.3 through 9.5.2 enabled the OAuth 2.0 refre…5.4
- CVE-2026-81922Concrete CMS before 9.5.3 did not enforce a per-page authori…2.7
- CVE-2026-81923In Concrete CMS before 9.5.3, the SEO Bulk Update Meta Tags …2.7
- CVE-2026-81924Concrete CMS before 9.5.3 is vulnerable to Cross-Site Reques…6.5
- CVE-2026-81925Concrete CMS before 9.5.3 improperly neutralized a user-supp…6.1
- CVE-2026-81926Concrete CMS 9.4.0 through 9.5.2 did not escape colliding pa…6.1
- CVE-2026-81928Net::DNS versions before 1.57 for Perl allow memory exhausti…7.5
- CVE-2026-8193A weakness has been identified in Akaunting 3.1.21. This iss…6.3
- CVE-2026-81931Unrestricted Upload of File with Dangerous Type in the produ…4.8
- CVE-2026-81933IBM Guardium Data Protection 12.2 is vulnerable to a SQL inj…8.8
- CVE-2026-81934Redis contains a use-after-free vulnerability in the 'tlsPro…7.1
- CVE-2026-81937IBM Guardium Data Protection 12.2 is vulnerable to a command…7.2
Are you affected by CVE-2026-81927?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
