CVE-2026-18117
Last modified
CVE-2026-18117 is a high-severity vulnerability rated 7.3/10 on the CVSS scale. 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. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Concrete CMS | Concrete CMS | >= 9.0.0, <= 9.5.2 |
References
Timeline
- Published
- Last Modified
- Status
- Undergoing Analysis
Frequently Asked Questions
What is CVE-2026-18117?
How severe is CVE-2026-18117?
How do I fix CVE-2026-18117?
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-1811A flaw has been found in bolo-blog bolo-solo up to 2.6.4. Th…8.8
- CVE-2026-18110Concrete CMS 9 (9.0.0 through 9.5.2) does not perform an aut…8.7
- CVE-2026-18111Concrete CMS 9 before 9.5.3 was vulnerable to stored cross-s…8.5
- CVE-2026-18113In Concrete CMS 9.0 to 9.5.2, the Top Navigation Bar block d…7.5
- CVE-2026-18115Concrete CMS 9.2.0 to 9.5.2 did not enforce per-field edit_u…7.4
- CVE-2026-18116Concrete CMS 8.3.0 to 9.5.2 stored calendar event names with…7.3
- CVE-2026-18119Concrete CMS below 9.5.3 did not sanitize custom style value…9
- CVE-2026-1812A vulnerability has been found in bolo-blog bolo-solo up to …9.8
- CVE-2026-18120Concrete CMS before 9.5.3 exposed a legacy Express entry sea…6.3
- CVE-2026-18121Concrete CMS 9.5.2 and below is vulnerable to an authorizati…6.3
- CVE-2026-18122Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint e…6
- CVE-2026-18125An out-of-bounds read in the Agent of Ivanti Endpoint Manage…7.5
Are you affected by CVE-2026-18117?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
