CVE-2026-8340: Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion

low Affects concrete5/concrete5. Feed 2026.10.29.1, updated 2026-10-28; published 2026-05-26; advisory modified 2026-09-10.

Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion

Package: concrete5/concrete5 Composer
Affected versions: <9.5.1
Fixed in: 9.5.1
Severity: low
Exploitation: not on CISA KEV · EPSS 0% (1.0th percentile)
Published: 2026-05-26
Source: osv.dev

References

CWE-352

NVD record concrete5/concrete5 advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

Related advisories

CVE-2020-11476 high Unrestricted Uploads in Concrete5 same package: concrete5/concrete5
CVE-2017-7725 medium Concrete CMS vulnerable to cross-site scripting (XSS) same package: concrete5/concrete5
CVE-2026-6826 medium Concrete CMS is vulnerable to unauthenticated file usage disclosure same package: concrete5/concrete5
CVE-2012-5181 medium Concrete5 Vulnerable to Cross-Site Scripting (XSS) same package: concrete5/concrete5
CVE-2024-1247 low Concrete CMS vulnerable to stored XSS via the Role Name field same package: concrete5/concrete5
CVE-2023-48648 medium Concrete CMS allows unauthorized access because directories can be created with insecure p same package: concrete5/concrete5