CVE-2026-10721: Concrete CMS: PHP Object Injection via unserialize() calls
Concrete CMS below 9.5.2 is vulnerable to PHP Object Injection via unserialize() calls in the in Permission, Cache, and Search components. An unauthenticated attacker may trigger arbitrary PHP object instantiation if a malicious serialized payload has been placed in the database. Concrete CMS thanks XananasX7 for reporting this issue.
Published Jun 10, 2026 · Updated Aug 12, 2026
Affected packages
concrete5/concrete5
- Ecosystem
- Composer (PHP)
- Affected
- < 9.5.2
- Fixed in
- 9.5.2
- Check
composer show concrete5/concrete5
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Concrete CMS below 9.5.2 is vulnerable to PHP Object Injection via unserialize() calls in the in Permission, Cache, and Search components. An unauthenticated attacker may trigger arbitrary PHP object instantiation if a malicious serialized payload has been placed in the database. Concrete CMS thanks XananasX7 for reporting this issue.
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-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, 2026CVE-2026-7881
Concrete CMS is subject to Insecure Direct Object Reference (IDOR) in the Express Entry Detail block
medium6.3May 22, 2026
