Public mode

No access to your tenant or devices. Every item links to its source. What this means

CVE-2026-18117

Concrete CMS 9.0.0 to 9.5.2 is vulnerable to Stored XSS in Custom Page Alias Name

CVSS 4.0 7.3 HIGHCheck source for fixed versionsKEV status unknown

Original advisory

cve-program · CVE-2026-18117

Published

Concrete CMS 9.0.0 through 9.5.3 is vulnerable to stored XSS via the custom page alias name (customAliasName) because the Edit Alias dialog applied only trim() to the submitted value and performed no input neutralization. An authenticated user holding canWrite (editor) permission on a page could store a malicious alias name that was later rendered unescaped in the administrative Sitemap panel, where it executed automatically in any administrator or editor session that opened the panel, allowing an editor to escalate to administrator through the victim's active session. 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:L/SC:N/SI:N/SA:N. Thanks Nguyen Manh Thuan for reporting.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-18117

Published

Concrete CMS

https://github.com/concretecms/concretecms

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "Concrete CMS",
                    "product": "Concrete CMS",
                    "collectionURL": "https://github.com/concretecms/concretecms",
                    "repo": "https://github.com/concretecms/concretecms",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "9.0.0",
                            "lessThanOrEqual": "9.5.2",
                            "versionType": "git"
                        }
                    ],
                    "defaultStatus": "unaffected"
                }

Original source record · Cite this exact observation · Complete original publisher JSON