# CVE-2022-41876: ezplatform-graphql GraphQL queries can expose password hashes

> Unauthenticated GraphQL queries can expose password hashes of users who created or modified content, affecting Ibexa DXP and Open Source installations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-c7pc-pgf6-mfh5

## What is CVE-2022-41876?

CVE-2022-41876 is a high-severity vulnerability in ezsystems ezplatform-graphql, published on 10 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ezplatform-graphql is a GraphQL server implementation for Ibexa DXP and Ibexa Open Source. Versions prior to 2.3.12 and 1.0.13 are subject to Insecure Storage of Sensitive Information. Unauthenticated GraphQL queries for user accounts can expose password hashes of users that have created or modified content, typically administrators and editors. This issue has been patched in versions 2.3.12, and 1.0.13 on the 1.X branch. Users unable to upgrade can remove the "passwordHash" entry from "src/bundle/Resources/config/graphql/User.types.yaml" in the GraphQL package, and other properties like hash type, email, login if you prefer.

Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

4 open source packages ship an affected version, including ezsystems/ezplatform-graphql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezplatform-graphql` | Packagist | From 1.0.0-rc1 | 1.0.13 |
| `ezsystems/ezplatform-graphql` | Packagist | From 1.0.0-rc1 | 1.0.13 |
| `ezsystems/ezplatform-graphql` | Packagist | From 2.0.0-beta1 | 2.3.12 |
| `ezsystems/ezplatform-graphql` | Packagist | From 2.0.0-beta1 | 2.3.12 |

Products: Ibexa Ezplatform-Graphql.

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

Upgrade ezsystems/ezplatform-graphql to a fixed version for your release line: 1.0.13 or 2.3.12.

## Is CVE-2022-41876 being exploited?

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

Public exploit code:

- PoC for CVE-2022-41876 (github_poc): https://github.com/Skileau/CVE-2022-41876

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41876 is a high-severity vulnerability in ezsystems ezplatform-graphql, published on 10 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41876 in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezplatform-graphql (Packagist): affected from 1.0.0-rc1; fixed in 1.0.13
- ezsystems/ezplatform-graphql (Packagist): affected from 1.0.0-rc1; fixed in 1.0.13
- ezsystems/ezplatform-graphql (Packagist): affected from 2.0.0-beta1; fixed in 2.3.12
- ezsystems/ezplatform-graphql (Packagist): affected from 2.0.0-beta1; fixed in 2.3.12

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

## Sources

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

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