Password-hash disclosure via exposed GraphQL user fields
Published Nov 10, 2022 · Updated Apr 23, 2025
Information disclosure in Ibexa eZ Platform GraphQL before 1.0.13 and from 2.0.0-beta1 through 2.3.11 allows remote attackers to read password hashes. The User.types.yaml GraphQL schema publishes the passwordHash field and related account properties without restricting unauthenticated user queries. Any exposed account that has created or modified content, commonly an administrator or editor, can have its password hash, hash type, email address, and login name disclosed.
Summary
What happened
Information disclosure in Ibexa eZ Platform GraphQL before 1.0.13 and from 2.0.0-beta1 through 2.3.11 allows remote attackers to read password hashes. The User.types.yaml GraphQL schema publishes the passwordHash field and related account properties without restricting unauthenticated user queries. Any exposed account that has created or modified content, commonly an administrator or editor, can have its password hash, hash type, email address, and login name disclosed.
The record
- CVE
- CVE-2022-41876
- Published
- Nov 10, 2022
- Updated
- Apr 23, 2025
- Vendor
- Ibexa
- Product
- eZ Platform GraphQL
- Classifications
- CWE-200, CWE-922, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.13
- Affected versionversion=>= v2.0.0-beta1, < 2.3.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo