# CVE-2022-31092: SQL injection in pimcore

> Attackers can inject SQL via improper quoting in listing classes if developers pass unvalidated input, requiring an upgrade to Pimcore.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** 27 Jun 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-gvmf-wcx6-p974

## What is CVE-2022-31092?

CVE-2022-31092 is a high-severity SQL injection vulnerability in Pimcore Pimcore, published on 27 Jun 2022. 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. Pimcore offers developers listing classes to make querying data easier. This listing classes also allow to order or group the results based on one or more columns which should be quoted by default. The actual issue is that quoting is not done properly in both cases, so there's the theoretical possibility to inject custom SQL if the developer is using this methods with input data and not doing proper input validation in advance and so relies on the auto-quoting being done by the listing classes. This issue has been resolved in version 10.4.4. Users are advised to upgrade or to apple the patch manually. There are no known workarounds for this issue.

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

## Which versions are affected by CVE-2022-31092?

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 | 10.4.4 |
| `pimcore/pimcore` | Packagist | All versions | 10.4.4 |

Products: Pimcore Pimcore.

## How do I fix CVE-2022-31092?

Upgrade pimcore/pimcore to 10.4.4 or later.

## Is CVE-2022-31092 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31092 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-47637](https://insights.sbomify.com/CVE-2023-47637/): SQL Injection in Admin Grid Filter API in Pimcore (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31092 and fix it if it is affected.

What it is: CVE-2022-31092 is a high-severity SQL injection vulnerability in Pimcore Pimcore, published on 27 Jun 2022. 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-2022-31092 exists.

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

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

## Sources

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

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