CVE Catalog

CVE-2026-8417

HighCVSS 8.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.12%

2th percentile - higher than 2% of all known CVEs

Summary

Concrete CMS 9.5.0 and below does not validate a CSRF token before processing requests to /dashboard/extend/update/do_update/<pkgHandle>. An attacker can force an authenticated administrator to trigger a package upgrade via a single cross-site navigation.

Risk Assessment

The risk is that an attacker can force an administrator to perform an unauthorized package upgrade, potentially leading to malicious code installation or system instability.

Recommendation

Upgrade Concrete CMS to a version newer than 9.5.0, which includes a fix for CSRF token validation on this endpoint.

Other vulnerabilities in Concrete CMS

See all
Original NVD description (English source)

Concrete CMS 9.5.0 and below does not validate a CSRF token before processing requests to /dashboard/extend/update/do_update/<pkgHandle>. The do_update() method in concrete/controllers/single_page/dashboard/extend/update.php checks only canInstallPackages() before executing upgradeCoreData() and upgrade() on the named package's controller. Because the endpoint is a state-changing GET route with no token enforcement, an attacker can force an authenticated administrator to trigger a package upgrade via a single cross-site navigation.In order to be vulnerable, the victim must be passing canInstallPackages() and and a target package must already be already installed. 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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS