What is GHSA-3P7G-WRGG-WQ45?

GHSA-3P7G-WRGG-WQ45 is a critical-severity security vulnerability in ibexa/graphql (composer), affecting versions >= 2.5.0, < 2.5.31. It is fixed in 2.5.31, 4.2.3, 3.3.28.

Which versions of ibexa/graphql are affected by GHSA-3P7G-WRGG-WQ45?

ibexa/graphql (composer) versions >= 2.5.0, < 2.5.31 is affected.

Is there a fix for GHSA-3P7G-WRGG-WQ45?

Yes. GHSA-3P7G-WRGG-WQ45 is fixed in 2.5.31, 4.2.3, 3.3.28. Upgrade to this version or later.

Is GHSA-3P7G-WRGG-WQ45 exploitable, and should I be worried?

Whether GHSA-3P7G-WRGG-WQ45 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-3P7G-WRGG-WQ45 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-3P7G-WRGG-WQ45?

Upgrade: ibexa/graphql to 2.5.31 or later, ibexa/graphql to 4.2.3 or later, ibexa/graphql to 3.3.28 or later.

GHSA-3P7G-WRGG-WQ45 in ibexa/graphql

Q: Which versions of ibexa/graphql are affected by GHSA-3P7G-WRGG-WQ45?

ibexa/graphql (composer) versions >= 2.5.0, < 2.5.31 is affected.

Q: Is there a fix for GHSA-3P7G-WRGG-WQ45?

Yes. GHSA-3P7G-WRGG-WQ45 is fixed in 2.5.31, 4.2.3, 3.3.28. Upgrade to this version or later.

Q: Is GHSA-3P7G-WRGG-WQ45 exploitable, and should I be worried?

Whether GHSA-3P7G-WRGG-WQ45 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-3P7G-WRGG-WQ45 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-3P7G-WRGG-WQ45?

Upgrade: ibexa/graphql to 2.5.31 or later, ibexa/graphql to 4.2.3 or later, ibexa/graphql to 3.3.28 or later.

Summary

GraphQL queries can expose password hashes

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.

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.

Affected versions

ibexa/graphql (>= 2.5.0, < 2.5.31) ibexa/graphql (>= 4.2.0, < 4.2.3) ibexa/graphql (>= 3.3.0, < 3.3.28)

Security releases

ibexa/graphql → 2.5.31 (composer) ibexa/graphql → 4.2.3 (composer) ibexa/graphql → 3.3.28 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is GHSA-3P7G-WRGG-WQ45? GHSA-3P7G-WRGG-WQ45 is a critical-severity security vulnerability in ibexa/graphql (composer), affecting versions >= 2.5.0, < 2.5.31. It is fixed in 2.5.31, 4.2.3, 3.3.28.
Which versions of ibexa/graphql are affected by GHSA-3P7G-WRGG-WQ45? ibexa/graphql (composer) versions >= 2.5.0, < 2.5.31 is affected.
Is there a fix for GHSA-3P7G-WRGG-WQ45? Yes. GHSA-3P7G-WRGG-WQ45 is fixed in 2.5.31, 4.2.3, 3.3.28. Upgrade to this version or later.
Is GHSA-3P7G-WRGG-WQ45 exploitable, and should I be worried? Whether GHSA-3P7G-WRGG-WQ45 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-3P7G-WRGG-WQ45 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-3P7G-WRGG-WQ45?
- Upgrade ibexa/graphql to 2.5.31 or later
- Upgrade ibexa/graphql to 4.2.3 or later
- Upgrade ibexa/graphql to 3.3.28 or later