CVE-2026-55212Public exploitNetwork attack vector

Editor-level schema modification via incorrect permission guard

Published Jul 9, 2026 · Updated Jul 9, 2026

Improper authorization in Pimcore before 2025.4.6 and 2026.1.0 through 2026.1.5 allows remote authenticated users to create class definitions. The Studio API CreateController checks the objects permission instead of the class-definition permission, while malformed UIDs reach model-layer validation and can return internal exceptions. A valid session with objects permission and the Studio API enabled is required; class creation generates database tables and PHP class files, while stack-trace exposure depends on server configuration.

CVSS severity7.1
High
EPSS probability0.35%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authorization in Pimcore before 2025.4.6 and 2026.1.0 through 2026.1.5 allows remote authenticated users to create class definitions. The Studio API CreateController checks the objects permission instead of the class-definition permission, while malformed UIDs reach model-layer validation and can return internal exceptions. A valid session with objects permission and the Studio API enabled is required; class creation generates database tables and PHP class files, while stack-trace exposure depends on server configuration.

The record

CVE
CVE-2026-55212
Published
Jul 9, 2026
Updated
Jul 9, 2026
Vendor
Pimcore
Product
Pimcore
Classifications
CWE-20, CWE-285, T1068
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 9, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 9, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2025.4.6
  2. Affected versionversion=>= 2026.1.0, < 2026.1.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Pimcore · Pimcoreversion=< 2025.4.6; version=>= 2026.1.0, < 2026.1.6

Published CVSS scores

7.1GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-20Improper Input Validation
CWE-285Improper Authorization
T1068Exploitation for Privilege Escalation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo