CVE-2026-8428

HIGH

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

Title source: cna
STIX 2.1

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.

References (1)

Core 1

Scores

CVSS v3 8.8
EPSS 0.0012
EPSS Percentile 2.3%
Attack Vector NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CISA SSVC

Vulnrichment
Exploitation none
Automatable no
Technical Impact total

Details

CWE
CWE-352 CWE-829
Status published
Products (2)
Concrete CMS/Concrete CMS 5.0 - 9.5.0
concretecms/concrete_cms < 9.5.1
Published May 21, 2026
Tracked Since May 22, 2026