VYPR
High severity8.8NVD Advisory· Published May 21, 2026· Updated May 26, 2026

CVE-2026-8417

CVE-2026-8417

Description

Concrete CMS 9.5.0 and below does not validate a CSRF token before processing requests to /dashboard/extend/update/do_update/. 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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
concrete5/concrete5Packagist
< 9.5.19.5.1

Affected products

3
  • Concrete5/Concrete5inferred3 versions
    <=9.5.0+ 2 more
    • (no CPE)range: <=9.5.0
    • cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:*range: <9.5.1
    • (no CPE)range: <=9.5.0

Patches

Vulnerability mechanics

References

3

News mentions

0

No linked articles in our index yet.