concrete5/concrete5
Affected
- introduced
0, fixed9.5.1(ecosystem)
Fixed versions
9.5.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-8417
Concrete does not validate a CSRF token before processing requests to /dashboard/extend/update/do_update/<pkgHandle>
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 thanks @maru1009 for reporting this issue.
High Basis: The source's own band: HIGH
0, fixed 9.5.1 (ecosystem)9.5.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0