← Browse

CVE-2026-8140

Low

No strong exploitation signal.

CVSS base
6.5 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS — probability of exploitation (30 days)
0.1%
2.0th percentile
CISA KEV
Not listed
Weakness / dates
CWE-352
Published 2026-05-21 · modified 2026-07-23

CVSS breakdown

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

Attack VectorNNetwork
Attack ComplexityLLow
Privileges RequiredNNone
User InteractionRRequired
ScopeUUnchanged
ConfidentialityNNone
IntegrityHHigh
AvailabilityNNone

Timeline

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.

Affected

concretecms

References

Official: NVD · CVE.org