CVE-2024-57190: Erxes <1.6.1 is vulnerable to Incorrect Access Control
Source CVE Database V5
Not known to be exploited : upgrade to 1.6.1 as a priority.
Data as of 26 Oct 2026, 17:16 UTC
Rated Critical by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.1
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade erxes/erxes to 1.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHuberxes/erxespkg:github/erxes/erxesOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately assess their use of Erxes and identify any instances running versions prior to 1.6.1. The primary mitigation is to upgrade to Erxes version 1.6.1 or later, where this access control flaw has been addressed. If upgrading is not immediately feasible, organizations should implement strict network-level access controls to restrict access to GraphQL endpoints only to trusted internal IPs or VPN users. Web application firewalls (WAFs) can be configured to detect and block suspicious "User" header manipulations. Additionally, monitoring and logging HTTP headers for anomalous values can help detect exploitation attempts. Organizations should conduct thorough audits of user activity and access logs to identify any unauthorized access. Implementing strong authentication and authorization mechanisms at the application layer, including validation of HTTP headers and tokens, is critical. Finally, organizations should prepare incident response plans specific to this vulnerability and educate their security teams about the risk and detection methods.
Description
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.