CVE-2026-18119 Concrete CMS CVE debrief

Who should care

Defenders responsible for Concrete CMS installations, especially those with editor-level users, should assess exposure and prioritize patching or mitigation. This includes reviewing the version of Concrete CMS in use, assessing the access levels of users, and implementing compensating controls where necessary. Defenders should also monitor for suspicious activity in administrator sessions and review relevant logs for exposed assets that need extra review.

Why it matters

CVE-2026-18119 is a stored cross-site scripting vulnerability in Concrete CMS that allows editor-level users to execute script in administrator sessions, potentially leading to privilege escalation. Defenders should prioritize patching or mitigating this vulnerability, especially in systems where editor-level users have access to the Block Design dialog.

• Potential privilege escalation from editor-level to administrator-level access
• Execution of script in administrator sessions
• Possible modification of administrator actions or access to sensitive data

Technical summary

The vulnerability is caused by unsanitized custom style values in the Block Design dialog, which are written into page CSS via a DOM sink. This allows an editor-level user to inject malicious script, potentially leading to privilege escalation. The vulnerability affects Concrete CMS versions below 9.5.3, and defenders should prioritize patching or mitigating this vulnerability, especially in systems where editor-level users have access to the Block Design dialog. The vulnerability's technical framing indicates that it is a legitimate concern, but the exact scope of affected systems is not explicitly stated.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially in systems where editor-level users have access to the Block Design dialog.

Recommended defensive actions

• Patch Concrete CMS to version 9.5.3 or later
• Restrict access to the Block Design dialog for editor-level users
• Monitor for suspicious activity in administrator sessions
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was reported by Nguyen Manh Thuan and assigned a CVSS v4.0 score of 7.0 by the Concrete CMS security team. The CVE record was published on 2026-09-14T20:16:42.563Z and has not been modified since then. The vulnerability affects Concrete CMS versions below 9.5.3, and defenders should verify the version of Concrete CMS in use and assess exposure. The vulnerability's source grounding indicates that it is a legitimate concern, but the exact scope of affected systems is not explicitly stated. Defenders should review the

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.