CVE-2024-57189: n/a
Source CVE Database V5
Not known to be exploited : upgrade to 1.6.2 soon.
Data as of 25 Oct 2026, 19:02 UTC
Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.2
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 2026-10-25.
What to do
Upgrade erxes/erxes to 1.6.2.
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
1. Upgrade Erxes to version 1.6.2 or later where this vulnerability is fixed. 2. If immediate upgrade is not possible, restrict access to the GraphQL API, especially the importHistoriesCreate mutation, to trusted users only and monitor for suspicious activity. 3. Implement strict input validation and sanitization on file path parameters in GraphQL mutations to prevent path traversal. 4. Employ application-layer firewalls or Web Application Firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting the importHistoriesCreate mutation. 5. Conduct regular audits of user accounts and permissions to minimize the risk of credential compromise and insider threats. 6. Monitor logs for unusual file write operations or unexpected changes in the filesystem related to the Erxes application. 7. Isolate the Erxes application environment with least privilege principles to limit the impact of any successful exploitation. 8. Educate users about phishing and credential security to reduce the risk of unauthorized authentication.
Description
In Erxes <1.6.2, an authenticated attacker can write to arbitrary files on the system using a Path Traversal vulnerability in the importHistoriesCreate GraphQL mutation handler.