CVE-2026-7882: Concrete CMS is vulnerable to unauthorized file deletion
Concrete CMS 9.5.0 and below is vulnerable to unauthorized file deletion due to an Inverted CSRF token check in the DeleteFile controller. The code throws an error when the token IS valid and proceeds with file deletion when the token is invalid or missing.
Published May 22, 2026 · Updated Jun 24, 2026
Affected packages
concrete5/concrete5
- Ecosystem
- Composer (PHP)
- Affected
- < 9.5.1
- Fixed in
- 9.5.1
- Check
composer show concrete5/concrete5
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Concrete CMS 9.5.0 and below is vulnerable to unauthorized file deletion due to an Inverted CSRF token check in the DeleteFile controller. The code throws an error when the token IS valid and proceeds with file deletion when the token is invalid or missing. This effectively disables CSRF protection for the file deletion endpoint, allowing cross-site request forgery attacks against users who have permission to edit conversation messages.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-10721
Concrete CMS: PHP Object Injection via unserialize() calls
high8.4Jun 10, 2026CVE-2026-7888
Concrete CMS is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components
high8.4Jun 3, 2026CVE-2026-8340
Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion
low2.3May 26, 2026CVE-2026-8347
Concrete CMS is vulnerable to IDOR + wrong-authorization-level in the Express association Reorder dialog
low2.3May 26, 2026CVE-2026-8353
Concrete CMS is vulnerable to Stored XSS via page name in the Atomik theme
low2.1May 26, 2026CVE-2026-7879
Concrete CMS has an unauthorized file access issue
medium6.3May 22, 2026
