# CVE-2026-55208: Pimcore: SQL Injection via Column Name in DateFilter allows authenticated user to extract arbitrary database data including admin password hashes

> Authenticated attackers can extract sensitive database data, including admin password hashes, via SQL injection in the DateFilter column key parameter.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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-79cw-hfcc-7mw9

## What is CVE-2026-55208?

CVE-2026-55208 is a high-severity SQL injection 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 Studio Backend Bundle is the backend bundle for Pimcore Studio. Prior to 2025.4.6 and 2026.1.6, an authenticated user can extract the admin password hash and other database content through time-based blind SQL injection in the DateFilter column key parameter. The POST /pimcore-studio/api/website-settings endpoint and other listing endpoints accept a columnFilters array where the key field is interpolated directly into SQL with manual backtick wrapping, allowing a backtick character to break out of quoting and append arbitrary SQL such as SLEEP() and IF() subqueries. This issue is fixed in versions 2025.4.6 and 2026.1.6.

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

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

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 | 2025.4.6 |
| `pimcore/studio-backend-bundle` | Packagist | All versions | 2025.4.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-55208?

Upgrade pimcore/studio-backend-bundle to a fixed version for your release line: 2025.4.6 or 2026.1.6.

## Is CVE-2026-55208 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55208 is a high-severity SQL injection 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-55208 exists.

Affected packages and fixed versions:
- pimcore/studio-backend-bundle (Packagist): affected all versions; fixed in 2025.4.6
- pimcore/studio-backend-bundle (Packagist): affected all versions; fixed in 2025.4.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-55208/ (Markdown: https://insights.sbomify.com/CVE-2026-55208/index.md)
```

## Sources

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

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