CVE-2026-8428: CSRF token is not validated in the core CMS update controller for Concrete CMS 9.5.0 and below
Concrete CMS 9.5.0 and below emits a CSRF token in the localavailableupdate.php view ($token->output('doupdate')) but the corresponding doupdate() method in concrete/controllers/singlepage/dashboard/system/update/update.php never calls $this->token->validate('doupdate'). The form is rendered as a POST form, meaning the token reaches the browser, but because the controller discards it without verification, an attacker can craft a cross-site POST that triggers a core CMS update to an attacker-specified version string. In order to be vulnerable, theictim must be passing canUpgrade()anda valid update version must be present under DIRCOREUPDATES. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 7.5 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks https://github.com/maru1009 for reporting.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Restrict ability to trigger core update actions (e.g., limit access to the Concrete CMS dashboard/system/update endpoint so only trusted users can reach it), since the do_update controller for Concrete CMS 9.5.0 and below does not validate CSRF tokens.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8428?
The severity of CVE-2026-8428 is high with a CVSS score of 7.5.
How do I fix CVE-2026-8428?
To fix CVE-2026-8428, ensure that the do_update() method in Concrete CMS properly validates the CSRF token.
Which versions of Concrete CMS are affected by CVE-2026-8428?
CVE-2026-8428 affects Concrete CMS versions 9.5.0 and below.
What type of vulnerability is CVE-2026-8428?
CVE-2026-8428 is a Cross-Site Request Forgery (CSRF) vulnerability.
When was CVE-2026-8428 published?
CVE-2026-8428 was published on May 21, 2026.