GHSA-3p7g-wrgg-wq45 — ibexa/graphql
Fix: ibexa/graphql@5ae5fb4GHSA-3p7g-wrgg-wq45 is a security vulnerability in ibexa/graphql. A fix is available for ibexa/graphql — see the affected versions and patch details below.
GraphQL queries can expose password hashes
Real-World Exposure
ibexa/graphql🐘ibexa/graphql🐘ibexa/graphqlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Unauthenticated GraphQL queries for user accounts can expose password hashes of users that have created or modified content, typically but not necessarily limited to administrators and editors.
Patches
Affected versions: Ibexa DXP v3.3.*, v4.2.*, eZ Platform v2.5.* Resolving versions: Ibexa DXP v3.3.28, v4.2.3, eZ Platform v2.5.31
Workarounds
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.
References
This issue was reported to us by Philippe Tranca ("trancap") of the company Lexfo. We are very grateful for their research, and responsible disclosure to us of this critical vulnerability.
For more information
If you have any questions or comments about this advisory, please contact Support via your service portal.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ibexa/graphql | ≥ 2.5.0&&< 2.5.31 | 2.5.31composer require ibexa/graphql:^2.5.31 |
| 🐘Packagist | ibexa/graphql | ≥ 4.2.0&&< 4.2.3 | 4.2.3composer require ibexa/graphql:^4.2.3 |
| 🐘Packagist | ibexa/graphql | ≥ 3.3.0&&< 3.3.28 | 3.3.28composer require ibexa/graphql:^3.3.28 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/graphql to 2.5.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3p7g-wrgg-wq45 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3p7g-wrgg-wq45 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3p7g-wrgg-wq45. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3p7g-wrgg-wq45 in your dependencies?
O3 Security finds GHSA-3p7g-wrgg-wq45 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.