CVE-2026-18117 Concretecms CVE debrief

Who should care

Concrete CMS administrators, editors, and users with canWrite permissions should assess exposure and prioritize remediation. They should review and update Concrete CMS to version 9.5.4 or later, restrict canWrite (editor) permissions to trusted users, and monitor Sitemap panel usage for suspicious activity.

Why it matters

CVE-2026-18117 is a stored XSS vulnerability in Concrete CMS that allows an authenticated editor to escalate privileges to administrator, potentially impacting site integrity and user data. Defenders should verify exposure, prioritize remediation, and monitor for suspicious activity.

• Privilege escalation from editor to administrator
• Potential for malicious code execution in the administrative Sitemap panel
• Possible impact on site integrity and user data
• Requires verification of affected versions and remediation status

Technical summary

The vulnerability exists due to insufficient input neutralization in the custom page alias name (customAliasName) field. An authenticated user with canWrite (editor) permission can store a malicious alias name that is later rendered unescaped in the administrative Sitemap panel, allowing for privilege escalation to administrator. This issue allows an editor to execute arbitrary code in the context of an administrator's session, impacting site integrity and user data. The vulnerability was reported by Nguyen Manh Thuan and assigned a CVSS v4.0 score of 7.3 by the Concrete CMS security team.

Defensive priority

High

Recommended defensive actions

• Review and update Concrete CMS to version 9.5.4 or later
• Restrict canWrite (editor) permissions to trusted users
• Monitor Sitemap panel usage for suspicious activity
• Implement additional input validation and sanitization for custom page alias names
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was reported by Nguyen Manh Thuan and assigned a CVSS v4.0 score of 7.3 by the Concrete CMS security team. The issue is caused by insufficient input neutralization in the custom page alias name (customAliasName) field. Defenders should verify exposure, prioritize remediation, and monitor for suspicious activity in the Sitemap panel usage.

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.