Advisory

GHSA-jr5g-qv3g-rxxx

Also known as: CVE-2026-8417

Summary

Concrete does not validate a CSRF token before processing requests to /dashboard/extend/update/do_update/<pkgHandle>

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-21 21:30 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

concrete5/concrete5

Packagist · All systems

Affected

  • introduced 0, fixed 9.5.1 (ecosystem)

Fixed versions

9.5.1

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences