Quick answers
- Is CVE-2024-57190 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-57190 being exploited in the wild.
- How severe is CVE-2024-57190?
- Medium severity, with a CVSS score of 4, published 10 June 2025.
- Which products and versions are affected?
- erxes (npm) SEMVER:introduced=0,fixed=1.6.1.
- Is there a fix for CVE-2024-57190?
- Yes. erxes (npm): upgrade to 1.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-57190 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2024-57190?
- Check whether you run erxes (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- erxes (npm): upgrade to 1.6.1 or later
npm install erxes@1.6.1
Technical details
Erxes versions prior to 1.6.1 contain an authentication bypass vulnerability in the GraphQL API layer. The vulnerability exists in the user authentication middleware (userMiddleware.ts), which accepts a "User" HTTP header at face value without validating its authenticity, allowing an attacker to specify any user ID to impersonate. The attack requires only network access to a reachable GraphQL endpoint (no prior authentication or user interaction needed). An attacker can exploit this to read sensitive customer data, modify configurations, or perform actions as any user in the system. The vulnerability is fixed in version 1.6.1 via commit 4ed2ca7.
Affected products
- Erxes Erxes < 1.6.1
Identifiers
- CVE-2024-57190
- GHSA-7rhv-xm4q-wh42
Timeline
- 2025-06-10: disclosed
- 2025-06-10: patched: Fixed in version 1.6.1