Concrete CMS 8.3.0 to 9.5.2 stored calendar event names without sanitization and rendered them without HTML escaping in the workflow approval and… (CVE-2026-18116)
Concrete CMS 8.3.0 to 9.5.2 stored calendar event names without sanitization and rendered them without HTML escaping in the workflow approval and deletion notifications shown in the dashboard "Waiting For Me" block. A registered user permitted to add events to a calendar governed by an approval workflow could submit an event whose name contained a script payload, which then executed in an administrator's browser when the pending request was displayed and could be used to create a new administrator account. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 7.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks v01demort for reporting.
AI Analysis
Technical Summary
Concrete CMS versions 8.3.0 to 9.5.2 improperly handle calendar event names by storing them without sanitization and rendering them without HTML escaping in workflow approval and deletion notifications displayed in the dashboard's "Waiting For Me" block. This stored XSS vulnerability allows a registered user with event creation privileges to inject script payloads that execute in an administrator's browser when viewing pending requests. Exploitation can lead to privilege escalation, including creating a new administrator account. The vulnerability is tracked as CVE-2026-18116 and has a CVSS v4.0 score of 7.3 (AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N).
Potential Impact
Successful exploitation allows an attacker with event creation permissions to execute arbitrary JavaScript in the context of an administrator's browser. This can lead to privilege escalation, including the creation of new administrator accounts, compromising the integrity and control of the CMS environment. The vulnerability affects the workflow approval and deletion notification processes, exposing administrators to malicious script execution when reviewing pending calendar events.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict calendar event creation permissions to trusted users only and monitor for suspicious activity related to event names. Avoid displaying untrusted input in administrative interfaces without proper sanitization or escaping.
Concrete CMS 8.3.0 to 9.5.2 stored calendar event names without sanitization and rendered them without HTML escaping in the workflow approval and… (CVE-2026-18116)
Description
Concrete CMS 8.3.0 to 9.5.2 stored calendar event names without sanitization and rendered them without HTML escaping in the workflow approval and deletion notifications shown in the dashboard "Waiting For Me" block. A registered user permitted to add events to a calendar governed by an approval workflow could submit an event whose name contained a script payload, which then executed in an administrator's browser when the pending request was displayed and could be used to create a new administrator account. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 7.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks v01demort for reporting.
CVSS v4.0
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Concrete CMS versions 8.3.0 to 9.5.2 improperly handle calendar event names by storing them without sanitization and rendering them without HTML escaping in workflow approval and deletion notifications displayed in the dashboard's "Waiting For Me" block. This stored XSS vulnerability allows a registered user with event creation privileges to inject script payloads that execute in an administrator's browser when viewing pending requests. Exploitation can lead to privilege escalation, including creating a new administrator account. The vulnerability is tracked as CVE-2026-18116 and has a CVSS v4.0 score of 7.3 (AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N).
Potential Impact
Successful exploitation allows an attacker with event creation permissions to execute arbitrary JavaScript in the context of an administrator's browser. This can lead to privilege escalation, including the creation of new administrator accounts, compromising the integrity and control of the CMS environment. The vulnerability affects the workflow approval and deletion notification processes, exposing administrators to malicious script execution when reviewing pending calendar events.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict calendar event creation permissions to trusted users only and monitor for suspicious activity related to event names. Avoid displaying untrusted input in administrative interfaces without proper sanitization or escaping.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mfc3-273r-x6gf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-18116"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6aa8a16455bf5e2cf5f3b7a8
Added to database: 09/15/2026, 01:37:40 UTC
Last enriched: 09/15/2026, 01:41:49 UTC
Last updated: 09/15/2026, 03:06:57 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.