CVE-2026-7888
PHP Object Injection in Concrete CMS
Publication date: 2026-06-03
Last updated on: 2026-06-03
Assigner: ConcreteCMS
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| concrete_cms | concrete_cms | to 9.5.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability can have a high impact on the affected system. An unauthenticated attacker with local access can exploit it to instantiate arbitrary PHP objects, potentially compromising confidentiality, integrity, and availability of the system.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the PHP Object Injection vulnerability in Concrete CMS versions below 9.5.2, you should upgrade to version 9.5.2 or later where the issue has been fixed.
The fix involves adding the allowed_classes restriction to the unserialize() calls in the Workflow, Form block, and File/Set components to prevent arbitrary PHP object instantiation.
Can you explain this vulnerability to me?
CVE-2026-7888 is a security vulnerability in Concrete CMS versions below 9.5.2 involving PHP Object Injection. This occurs because unserialize() calls in the Workflow, Form block, and File/Set components do not restrict allowed_classes, allowing an attacker to instantiate arbitrary PHP objects if a malicious serialized payload is placed in the database.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Concrete CMS allows PHP Object Injection, which can lead to high impacts on confidentiality, integrity, and availability of data.
Such impacts can potentially affect compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and system integrity.
However, the provided information does not explicitly state the direct effects on compliance with these standards.