# CVE-2026-55416: Pimcore: SQL Injection in Custom Reports via Malicious Report Configuration

> Authenticated users with report permissions can inject SQL via custom report configurations, allowing arbitrary database data disclosure, modification, or deletion.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-23rh-xw42-fq82

## What is CVE-2026-55416?

CVE-2026-55416 is a high-severity SQL injection vulnerability in pimcore, published on 14 Sep 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 11.5.19, 12.3.10, and 2026.1.6, an authenticated user with reports_config permission can place attacker-controlled SQL fragments in the sql, from, where, and groupby fields of a Custom Reports configuration processed by bundles/CustomReportsBundle/src/Tool/Adapter/Sql.php. The buildQueryString() method concatenates these values into a database query, while a blacklist omits dangerous constructs such as additional data-manipulation statements, comments, subqueries, and multiple statements. The getData() method also previously interpolated offset and limit values into a LIMIT clause without integer casting. Executing the configured report reaches fetchAllAssociative() with the constructed query and can disclose, modify, or delete arbitrary database data. This issue is fixed in versions 11.5.19, 12.3.10, and 2026.1.6.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 11.5.19 |
| `pimcore/pimcore` | Packagist | All versions | 11.5.19 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.10 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.10 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.6 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.6 |

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

Upgrade pimcore/pimcore to a fixed version for your release line: 11.5.19, 12.3.10 or 2026.1.6.

## Is CVE-2026-55416 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55416 is a high-severity SQL injection vulnerability in pimcore, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55416 in the wild and no public exploit code.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.5.19
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.5.19
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.10
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.10
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.6
- pimcore/pimcore (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-55416/ (Markdown: https://insights.sbomify.com/CVE-2026-55416/index.md)
```

## Sources

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

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