/

CVE-2026-55072

Severity:

HIGH RISK

(8.5)

SQL Injection (CWE-89) in Pimcore ClassDefinition Model

CVE-2026-55072

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-20, CWE-89

Impact:

Arbitrary database read and modification

Severity:

HIGH RISK

(8.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Pimcore contains a high-severity SQL injection vulnerability in ClassDefinition handling. An authenticated user with object-management permission may provide a specially crafted class identifier that can cause SQL syntax to be inserted into queries, potentially exposing or modifying arbitrary Pimcore database tables.

Affected context

The issue occurs in Pimcore versions before 2026.1.5 when an authenticated user has permission to manage objects and can submit a ClassDefinition UID. Risk is present when a data object using a Block field is later loaded and the stored class identifier is incorporated into an unquoted database table identifier. Partial validation of the identifier allows values with valid prefixes but unsafe trailing content.

Exploit preconditions

  • Attack surface: Pimcore object and ClassDefinition management functionality
  • Required access: An authenticated account with the relevant objects permission
  • Trigger point: Loading a data object containing a Block field
  • Why exploitation is possible: Name and ID validation checks only the beginning of the supplied value, while the resulting class ID is later used in an unquoted SQL identifier

Why this happens

The vulnerability combines incomplete input validation with unsafe construction of SQL identifiers. Validation applies a start anchor but does not require the entire ClassDefinition name or ID to match the intended format, allowing additional SQL syntax to remain. Later, Block loading incorporates the stored identifier into a query without safely delimiting or structurally validating it. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and also to CWE-20: Improper Input Validation.

Potential impact

  • An attacker may read arbitrary Pimcore database tables
  • Password hashes and other sensitive records could be disclosed
  • An attacker could modify or delete application data
  • Database integrity and application behavior could be compromised
  • The vulnerability could support broader compromise depending on database privileges

General mitigation guidance

Mitigation generally focuses on enforcing complete validation and preventing user-controlled identifiers from becoming SQL syntax.

Common defensive patterns include:

  • Require full-string matches against a strict allowlist for class names and identifiers
  • Reject unexpected characters, delimiters, whitespace, and trailing content
  • Use trusted internal mappings from validated identifiers to database objects rather than accepting table names directly
  • Apply database APIs that safely quote identifiers where dynamic identifiers are unavoidable
  • Keep application database accounts limited to the tables and operations they require
  • Treat object metadata and ClassDefinition values as untrusted until validated at every relevant boundary

How teams detect issues like this

Detection can include:

  • Static analysis rules for SQL query construction using concatenated or interpolated identifiers
  • Code review checks for regular expressions that anchor only the beginning of an input
  • Tests that verify complete-string validation and reject appended delimiters or SQL metacharacters
  • Monitoring for unusual ClassDefinition changes, object metadata updates, and database queries involving unexpected identifiers
  • Policy enforcement requiring parameterized values, approved identifier-mapping functions, and least-privilege database roles

Automated security review tools may help identify partial validation and dynamic SQL construction patterns.

Sources

SourceLink
github.comgithub.com/pimcore/pimcore/commit/33a0e1887e1e31b4283b016ac5440c35ea5697b4
github.comgithub.com/pimcore/pimcore/pull/19177
github.comgithub.com/pimcore/pimcore/releases/tag/v2026.1.5
github.comgithub.com/pimcore/pimcore/security/advisories/GHSA-2mhj-fhvg-v428

Frequently asked

questions

It may be exploitable through Pimcore's application interface when the affected functionality is exposed and the attacker has a qualifying authenticated account.

The attacker needs authentication and permission to submit or manage the relevant object and ClassDefinition data. Anonymous access alone is not generally sufficient.

Validate the complete ClassDefinition identifier against a strict allowlist and avoid incorporating user-controlled identifiers directly into SQL. Prefer trusted mappings and safe identifier-handling APIs.

Combine full-string input validation, parameterized database access, focused tests for trailing invalid content, code review of dynamic SQL, and least-privilege database permissions.

Find out what's already
exploitable in your codebase.