Home

Description

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

PUBLISHED Reserved 2026-05-12 | Published 2026-05-21 | Updated 2026-05-22 | Assigner ConcreteCMS




HIGH: 7.5CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Problem types

CWE-352 Cross-Site request forgery (CSRF)

CWE-829 Inclusion of functionality from untrusted control sphere

Product status

Default status
unaffected

5.0 (git)
affected

References

documentation.concretecms.org/...n-history/951-release-notes release-notes

cve.org (CVE-2026-8426)

nvd.nist.gov (CVE-2026-8426)

Download JSON