# CVE-2026-55212: Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation

> Standard editors can create class definitions due to incorrect permission checks, leading to privilege escalation and potential code execution via generated files.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-f97c-ph8j-8vff

## What is CVE-2026-55212?

CVE-2026-55212 is a high-severity missing authorization vulnerability in pimcore, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pimcore is an Open Source Data & Experience Management Platform. Prior to 2025.4.6 and 2026.1.6, the Studio API class definition creation endpoint POST /pimcore-studio/api/class/definition/configuration-view/detail/create is guarded by the objects permission instead of the classes permission, allowing a standard editor-level user to create class definitions without admin privileges. Class definition creation generates new database tables and PHP class files on the server, and missing API-layer UID format validation allows malformed UIDs to reach model-layer validation and return internal exceptions. This issue is fixed in versions 2025.4.6 and 2026.1.6.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-55212?

4 open source packages ship an affected version, including pimcore/studio-backend-bundle.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/studio-backend-bundle` | Packagist | All versions | 2026.1.6 |
| `pimcore/studio-backend-bundle` | Packagist | All versions | 2026.1.6 |
| `pimcore/studio-backend-bundle` | Packagist | From 2026.1.0 | 2026.1.6 |
| `pimcore/studio-backend-bundle` | Packagist | From 2026.1.0 | 2026.1.6 |

## How do I fix CVE-2026-55212?

Upgrade pimcore/studio-backend-bundle to 2026.1.6 or later.

## Is CVE-2026-55212 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55212 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55212 and fix it if it is affected.

What it is: CVE-2026-55212 is a high-severity missing authorization vulnerability in pimcore, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55212 exists.

Affected packages and fixed versions:
- pimcore/studio-backend-bundle (Packagist): affected all versions; fixed in 2026.1.6
- pimcore/studio-backend-bundle (Packagist): affected all versions; fixed in 2026.1.6
- pimcore/studio-backend-bundle (Packagist): affected from 2026.1.0; fixed in 2026.1.6
- pimcore/studio-backend-bundle (Packagist): affected from 2026.1.0; fixed in 2026.1.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55212/ (Markdown: https://insights.sbomify.com/CVE-2026-55212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55212
- OSV: https://osv.dev/vulnerability/CVE-2026-55212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55212/
Summaries are generated and may contain mistakes; the official description above is the record.