# CVE-2026-5394: Pimcore Platform v12.3.3 - SQL Injection in DataObject composite index handling

> An authenticated admin can inject SQL via DataObject composite index metadata, allowing unauthorized database access or modification.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Apr 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-r2f4-ff2p-xc64

## What is CVE-2026-5394?

CVE-2026-5394 is a high-severity SQL injection vulnerability in pimcore, published on 27 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated administrative user who can import or save DataObject class definitions can inject attacker-controlled composite index metadata and trigger unintended SQL execution in the backend.

This issue affects pimcore: 12.3.3.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

6 open source packages ship an affected version, including pimcore/pimcore.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 11.5.17 |
| `pimcore/pimcore` | Packagist | All versions | 11.5.17 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.7 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.7 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.3 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.3 |

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

Upgrade pimcore/pimcore to a fixed version for your release line: 11.5.17, 12.3.7 or 2026.1.3.

## Is CVE-2026-5394 being exploited?

There is no known exploitation of CVE-2026-5394 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5394 is a high-severity SQL injection vulnerability in pimcore, published on 27 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5394 in the wild and no public exploit code.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.5.17
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.5.17
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.7
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.7
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.3
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.3

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-5394/ (Markdown: https://insights.sbomify.com/CVE-2026-5394/index.md)
```

## Sources

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

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