CVE-2026-8428

CSRF token is not validated in the core CMS update controller for Concrete CMS 9.5.0 and below

State
Published
Severity
7.5 High
Published
May 21, 2026
Updated
May 22, 2026
Reserved
May 12, 2026

Read the record on cve.org

Description

Concrete CMS 9.5.0 and below emits a CSRF token in the local_available_update.php view ($token->output('do_update')) but the corresponding do_update() method in concrete/controllers/single_page/dashboard/system/update/update.php never calls $this->token->validate('do_update'). 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 DIR_CORE_UPDATES. 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.

Scores

CVSSScoreVectorSource
4.07.5 HighCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NConcreteCMS

Weaknesses

  • CWE-352 Cross-Site request forgery (CSRF)
  • CWE-829 Inclusion of functionality from untrusted control sphere

Affected Products

ProductVersions
Concrete CMSConcrete CMS
  • 5.0 through 9.5.0Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.