Advisory Database
  • Advisories
  • Dependency Scanning
  1. composer
  2. ›
  3. concrete5/concrete5
  4. ›
  5. CVE-2026-8417

CVE-2026-8417: Concrete does not validate a CSRF token before processing requests to `/dashboard/extend/update/do_update/<pkgHandle>`

May 21, 2026 (updated June 24, 2026)

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 thanks @maru1009 for reporting this issue.

References

  • documentation.concretecms.org/9-x/developers/introduction/version-history/951-release-notes
  • github.com/advisories/GHSA-jr5g-qv3g-rxxx
  • nvd.nist.gov/vuln/detail/CVE-2026-8417

Code Behaviors & Features

Detect and mitigate CVE-2026-8417 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 9.5.1

Fixed versions

  • 9.5.1

Solution

Upgrade to version 9.5.1 or above.

Impact 7.5 HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • CWE-352: Cross-Site Request Forgery (CSRF)

Source file

packagist/concrete5/concrete5/CVE-2026-8417.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Tue, 21 Jul 2026 00:18:14 +0000.