# CVE-2023-47637: SQL Injection in Admin Grid Filter API in Pimcore

> Authenticated backend users can execute arbitrary SQL via the grid filter API, allowing data modification and privilege escalation to admin level.

- **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:** 15 Nov 2023
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-72hh-xf79-429p

## What is CVE-2023-47637?

CVE-2023-47637 is a high-severity SQL injection vulnerability in Pimcore Pimcore, published on 15 Nov 2023. 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. In affected versions the `/admin/object/grid-proxy` endpoint calls `getFilterCondition()` on fields of classes to be filtered for, passing input from the request, and later executes the returned SQL.  One implementation of `getFilterCondition()` is in `Multiselect`, which does not normalize/escape/validate the passed value. Any backend user with very basic permissions can execute arbitrary SQL statements and thus alter any data or escalate their privileges to at least admin level. This vulnerability has been addressed in version 11.1.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2023-47637?

2 open source packages ship an affected version, including pimcore/pimcore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 11.1.1 |
| `pimcore/pimcore` | Packagist | All versions | 11.1.1 |

Products: Pimcore Pimcore.

## How do I fix CVE-2023-47637?

Upgrade pimcore/pimcore to 11.1.1 or later.

## Is CVE-2023-47637 being exploited?

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

## Other vulnerabilities in Pimcore Pimcore

- [CVE-2022-39365](https://insights.sbomify.com/CVE-2022-39365/): RCE vulnerability in Pimcore/Mail & Dynamic Text Layout (critical 9.8)
- [CVE-2019-18981](https://insights.sbomify.com/CVE-2019-18981/): Pimcore Access Control Issues (critical 9.8)
- [CVE-2019-18985](https://insights.sbomify.com/CVE-2019-18985/): Pimcore 2FA Vulnerable to Brute Forcing (critical 9.8)
- [CVE-2026-23492](https://insights.sbomify.com/CVE-2026-23492/): Pimcore has a Blind SQL Injection in Admin Search Find API due to an incomplete fix for CVE-2023-30848 (high 8.8)
- [CVE-2023-30848](https://insights.sbomify.com/CVE-2023-30848/): Pimcore SQL Injection Vulnerability in Admin Search Find API (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47637 and fix it if it is affected.

What it is: CVE-2023-47637 is a high-severity SQL injection vulnerability in Pimcore Pimcore, published on 15 Nov 2023. 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-2023-47637 exists.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.1.1
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.1.1

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

## Sources

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

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