CyberRota Analysis
AI-GeneratedAuthenticated users with object permissions in Pimcore versions prior to 2026.1.5 can exploit insufficient validation in ClassDefinition UID submissions to execute SQL injection attacks, potentially allowing unauthorized access to sensitive database information, including password hashes. Organizations using affected versions should prioritize upgrading to 2026.1.5 to mitigate this high-severity vulnerability and protect their data integrity. This issue is particularly critical for businesses relying on Pimcore for data and experience management.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Pimcore is an Open Source Data & Experience Management Platform. Prior to 2026.1.5, an authenticated user with the objects permission can submit a malicious ClassDefinition UID because the name and ID validation expressions in models/DataObject/ClassDefinition.php validate only the beginning of each value. When a data object of that class containing a Block field is loaded, Block::load in models/DataObject/ClassDefinition/Data/Block.php incorporates the stored class ID into an unquoted object table identifier, allowing the UID to supply SQL syntax. The resulting query can read or modify arbitrary Pimcore database tables, including disclosure of password hashes, and the flaw represents an incomplete validation hardening because earlier work added a start anchor without enforcing the end of the identifier. This issue is fixed in version 2026.1.5.