External risk intelligence

Pimcore DataObject Import Endpoint Vulnerability Allows Code and SQL Injection.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-55634

The vulnerability exists in an authenticated administrative or development API endpoint within a data management platform. While Pimcore instances can be internet-facing, access to this specific endpoint requires existing user authentication and specific object permissions, making it less likely to be exposed as a public-facing service compared to a gateway or unauthenticated edge service.

SQL Injection

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in Pimcore, an open-source data and experience management platform. The issue allows authenticated users to inject malicious code, potentially leading to arbitrary code execution and SQL injection. The primary concern is confirming if your organization uses this platform and if the affected versions are in use.

  • Injects code into data objects.
  • Allows code execution and data alteration.
  • Confirm Pimcore usage and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could gain the ability to execute arbitrary code or manipulate the database by exploiting a vulnerability in Pimcore's class-definition import functionality. This requires an authenticated user with object permissions to submit specially crafted input to an API endpoint. When objects of the affected class are later created, the injected PHP code runs, or malicious SQL statements are executed against the database.

  • Authenticated user with object permissions.
  • Importing class definitions with malicious input.
  • Arbitrary code execution and SQL injection.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated user with specific permissions to inject malicious code into PHP files or execute arbitrary SQL commands by manipulating class definitions. This could lead to the execution of attacker-controlled code when objects of a modified class are created, or unauthorized modifications to the database schema.

  • Affected asset: Customizable PHP classes and database schema.
  • Exposure: Injecting malicious code into class definitions.
  • Consequence: Arbitrary code execution and data integrity compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world remediation likely falls to the platform or application owners managing the Pimcore instance, supported by security teams for exposure analysis and infrastructure teams for patching or configuration. The first practical step is to identify all deployed Pimcore instances, determine their reachability and criticality, and pinpoint the accountable owner for each. Subsequently, a risk-based remediation plan should be developed, which may involve coordinating with the vendor, planning maintenance windows, or implementing temporary mitigations.

  • Platform owners should manage the issue.
  • Verify asset reachability and criticality.
  • Plan remediation based on assessed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Pimcore?

Pimcore is an open-source platform used for managing digital data, product information, and customer experiences. It provides developers and administrators with tools to define complex data structures, known as DataObjects, which organize information within a centralized system. These structures are integral to how the platform stores, retrieves, and displays content across various business applications.

What does CVE-2026-55634 mean for system security?

This vulnerability involves two weakness classes: Code Injection (CWE-94) and SQL Injection (CWE-89). It occurs because the system fails to validate input properly during class definition imports. Attackers can inject unauthorized PHP commands into generated class files or malicious SQL identifiers into database schema statements. When the platform processes these modified classes or schema structures, it inadvertently executes the attacker's instructions, potentially leading to unauthorized data access.

How is this Pimcore vulnerability triggered?

An attacker triggers this flaw by interacting with the class-definition import API endpoint while logged in as a user with object management permissions. The bug is activated when the system processes specifically crafted, malicious input during an import operation. Simply viewing or browsing objects does not trigger the vulnerability; it requires a specific, intentional action to import a compromised class definition that defines how data is stored or structured.

Is my Pimcore instance at risk according to Halo Surface Signal?

Halo Surface Signal notes that this vulnerability resides in an administrative or development API. While Pimcore instances can be internet-facing, this flaw specifically requires valid user authentication and existing object permissions to exploit. This makes it less accessible to automated, unauthenticated internet scanning compared to vulnerabilities found in public-facing gateways or unauthenticated edge services.

What is the first step to address CVE-2026-55634?

Your first step is to perform a software inventory to identify all deployed Pimcore instances and determine their current version numbers. If you are running a version prior to 11.5.19, 12.3.10, or 2026.1.6, prioritize upgrading your installation to the latest patched version provided by the vendor. Coordinate with your application owners to schedule this update, as applying the official fix is the most effective way to secure the class-definition import process.

References