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

CVE-2026-8426: Concrete CMS does not validate a CSRF token before processing requests to `/dashboard/extend/update/prepare_remote_upgrade/<remoteMPID>`

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/prepare_remote_upgrade/. An attacker who controls the remote package returned for a known marketplace item ID can overwrite the package PHP on disk and force its upgrade() method to execute in a single browser navigation. This results in remote code execution as the web server user.   In order to be vulnerable, the victim must be passing canInstallPackages, victim site must be connected to the Concrete marketplace; and the attacker controls the package returned for a marketplace item ID already installed on the victim site. 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-5rj5-gfmr-hrc3
  • nvd.nist.gov/vuln/detail/CVE-2026-8426

Code Behaviors & Features

Detect and mitigate CVE-2026-8426 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-8426.yml

Spotted a mistake? Edit the file on GitLab.

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

Page generated Thu, 16 Jul 2026 12:19:01 +0000.