CVE-2024-57190

CVE-2024-57190 is a high-severity improper authentication vulnerability in erxes (npm), affecting versions < 1.6.1. It is fixed in 1.6.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Erxes Incorrect Access Control vulnerability

Erxes <1.6.1 is vulnerable to Incorrect Access Control. An attacker can bypass authentication by providing a "User" HTTP header that contains any user, allowing them to talk to any GraphQL endpoint.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

Affected versions

erxes (< 1.6.1)

Security releases

erxes → 1.6.1 (npm)

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 environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade erxes to 1.6.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2024-57190? CVE-2024-57190 is a high-severity improper authentication vulnerability in erxes (npm), affecting versions < 1.6.1. It is fixed in 1.6.1. The application does not adequately verify the identity of a user, device, or process before granting access.
  2. Which versions of erxes are affected by CVE-2024-57190? erxes (npm) versions < 1.6.1 is affected.
  3. Is there a fix for CVE-2024-57190? Yes. CVE-2024-57190 is fixed in 1.6.1. Upgrade to this version or later.
  4. Is CVE-2024-57190 exploitable, and should I be worried? Whether CVE-2024-57190 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
  5. What actually determines whether CVE-2024-57190 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.
  6. How do I fix CVE-2024-57190? Upgrade erxes to 1.6.1 or later.

Other vulnerabilities in erxes

Stop the waste.
Protect your environment with Kodem.