CVE-2026-45162

Pimcore: Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction

Published Jul 17, 2026 CVSS 3.1 · 8 High EPSS < 1% KEV · Not listed
Description
Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.7, multiple Pimcore locations call PHP's unserialize() on data from database columns and filesystem files without the allowed_classes restriction, including lib/Tool/Authentication.php, models/Site/Dao.php, models/DataObject/ClassDefinition/CustomLayout/Dao.php, models/Tool/TmpStore/Dao.php, models/Asset/WebDAV/Service.php, and admin-ui-classic-bundle/src/Helper/Dashboard.php, enabling object injection and remote code execution if an attacker can control the serialized data source. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.

Analysis

AI-generated

Technical impact

The vulnerability exposes Pimcore installations prior to version 11.5.17 (LTS) and 12.3.7 to an unsafe deserialization flaw. Multiple code paths, including lib/Tool/Authentication.php, models/Site/Dao.php, and others, invoke PHP's unserialize() on data from database columns or filesystem files without using the allowed_classes restriction. When an attacker can control the content of the serialized data, object injection occurs, enabling remote code execution.

Affected Systems

Pimcore Open Source Data & Experience Management Platform, versions prior to 11.5.17 (LTS) and 12.3.7 are vulnerable. All affected installations before these releases must be considered at risk.

Risk and Exploitability

The CVSS score of 8 indicates high severity, while the EPSS score of less than 1% suggests a low probability of widespread exploitation. The vulnerability is not listed in the CISA KEV catalog. Likely exploitation requires an attacker to control the content of the serialized data source, implying that threat actors would need either local database access or a way to influence files that are deserialized by the application. This condition makes the attack vector more limited, but if the conditions are met, the impact could be complete compromise of the affected system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Pimcore to version 12.3.7 or 11.5.17 or later, where the unserialize() calls enforce an allowed_classes restriction.
  • Audit and cleanse the database fields and filesystem files that contain serialized data to remove any potentially malicious payloads after the upgrade.
  • Modify any remaining unserialize() calls in the codebase or adjust PHP configuration to set the allowed_classes parameter or to use a secure unserialize wrapper, ensuring deserialization is performed safely.

Generated by OpenCVE AI on July 30, 2026 at 23:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-36fc-7wjg-mfvj Pimcore has Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Pimcore
Pimcore pimcore
Vendors & Products Pimcore
Pimcore pimcore
Type Values Removed Values Added
Description Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.7, multiple Pimcore locations call PHP's unserialize() on data from database columns and filesystem files without the allowed_classes restriction, including lib/Tool/Authentication.php, models/Site/Dao.php, models/DataObject/ClassDefinition/CustomLayout/Dao.php, models/Tool/TmpStore/Dao.php, models/Asset/WebDAV/Service.php, and admin-ui-classic-bundle/src/Helper/Dashboard.php, enabling object injection and remote code execution if an attacker can control the serialized data source. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.
Title Pimcore: Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction
Weaknesses CWE-502
References
Metrics cvssV3_1

{'score': 8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 11:15 PM
Reserved
May 8, 2026, 8:44 PM
Status
Deferred
Published
Jul 17, 2026, 7:17 PM
Modified
Jul 22, 2026, 8:50 PM