No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 22 May 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 21 May 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Concretecms
Concretecms concrete Cms |
|
| Vendors & Products |
Concretecms
Concretecms concrete Cms |
Thu, 21 May 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Concrete CMS 9.5.0 and below does not validate a CSRF token before processing requests to /dashboard/extend/install/download/<remoteId>. The download() method in concrete/controllers/single_page/dashboard/extend/install.php checks only the canInstallPackages() permission before fetching a remote marketplace package and writing it to the server's DIR_PACKAGES directory. Because the endpoint is a state-changing GET route with no token enforcement, an attacker who can cause an authenticated administrator to visit a crafted page can force an arbitrary marketplace package to be downloaded. In order to be vulnerable, the victim must be passing canInstallPackages() and the site must be connected to the Concrete marketplace. 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. | |
| Title | Concrete CMS 9.5.0 and below is vulnerable to CSRF on download() in the package install controller | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: ConcreteCMS
Published:
Updated: 2026-05-22T12:13:59.064Z
Reserved: 2026-05-07T18:17:00.416Z
Link: CVE-2026-8140
Updated: 2026-05-22T12:13:54.600Z
Status : Received
Published: 2026-05-21T21:16:33.107
Modified: 2026-05-21T21:16:33.107
Link: CVE-2026-8140
No data.
OpenCVE Enrichment
Updated: 2026-05-21T22:45:21Z