CVE-2026-81911
Last modified
CVE-2026-81911 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. Concrete CMS versions 9.0.0 to 9.5.2 is vulnerable to Stored XSS in Board Custom Slot dialog. The custom_slot save_template endpoint authorizes the request only against the target board instance (canEditBoardContents()) and then persists the client-supplied selectedTemplateOption[collection] verbatim, rather than rebuilding the content object collection server-side and verifying that each item belongs to the authorized board's data pool. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
Description
Concrete CMS versions 9.0.0 to 9.5.2 is vulnerable to Stored XSS in Board Custom Slot dialog. The custom_slot save_template endpoint authorizes the request only against the target board instance (canEditBoardContents()) and then persists the client-supplied selectedTemplateOption[collection] verbatim, rather than rebuilding the content object collection server-side and verifying that each item belongs to the authorized board's data pool. A user with permission to edit the contents of at least one board instance can therefore store a forged summary object whose description field carries a JavaScript-bearing HTML payload. The default summary template renders the description field without output encoding, so the payload executes in the browser of any user who views the affected board slot, including anonymous front-end visitors and dashboard users who preview the resulting rule or block. This can enable session or action takeover and escalation toward an administrator. Concrete CMS versions below 9 do not include the Boards feature and are not affected. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.8 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Concretecms | Concrete Cms | >= 9.0.0, < 9.5.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-81911?
How severe is CVE-2026-81911?
How do I fix CVE-2026-81911?
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-81906Concrete CMS OAuth callback login path prior to version 9.5.…6.3
- CVE-2026-81907Concrete CMS 9.5.2 and below is vulnerable to Cross-Site Req…6.1
- CVE-2026-81908Concrete CMS 9.2.0 to 9.5.2 contain a missing authorization …6
- CVE-2026-81909Concrete CMS 9 through 9.5.2 is vulnerable to Missing Author…5.9
- CVE-2026-8191A vulnerability was identified in Wavlink NU516U1 M16U1_V240…8.8
- CVE-2026-81910Concrete CMS 9 through 9.5.2 is vulnerable to Server-Side Te…6.5
- CVE-2026-81912Concrete CMS before 9.5.3 is vulnerable to Cross-Site Reques…5.7
- CVE-2026-81913Concrete CMS versions 9.5.0 through 9.5.2 are vulnerable to …5.3
- CVE-2026-81915Concrete CMS below 9.5.3 does not perform an object-level au…5.1
- CVE-2026-81916Concrete CMS before 9.5.3 evaluated the authorization check …4.3
- CVE-2026-81917Concrete CMS below 9.5.3 does not apply HTML output escaping…5.4
- CVE-2026-81918Concrete CMS below 9.5.3 is vulnerable to Stored XSS via the…4.8
Are you affected by CVE-2026-81911?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
