# CVE-2026-44739: Pimcore: SQL Injection in Custom Reports Column Configuration

> An attacker with reports_config permission can execute arbitrary SQL queries to exfiltrate or manipulate database data in Pimcore.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-3234-gxc3-pq6f

## What is CVE-2026-44739?

CVE-2026-44739 is a high-severity SQL injection vulnerability in pimcore, published on 17 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.6, the columnConfigAction endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php passes malicious SQL configuration through CustomReportController:columnConfigAction, SqlAdapter::getColumns, SqlAdapter::buildQueryString, and Db::fetchAssociative(), allowing an attacker with the reports_config permission to use arbitrary SELECT queries, UNION statements, dangerous database functions, and error-based SQL injection to exfiltrate or manipulate database data. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.

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

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

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.6 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.6 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.2 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.2 |

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

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

## Is CVE-2026-44739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44739 is a high-severity SQL injection vulnerability in pimcore, published on 17 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44739 exists.

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.6
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.6
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.2
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.2

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

## Sources

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

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