CVE-2024-39173: calculator-boilerplate · Eval Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jul 2024
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
AI-suggested
To mitigate CVE-2024-39173, organizations should immediately audit the affected codebase to identify and remove all uses of the eval function, especially where it processes user input. Replace eval with safer alternatives such as JSON parsing or dedicated expression evaluators that do not execute arbitrary code. Implement strict input validation and sanitization to ensure only expected and safe data is processed. Employ security-focused code reviews and static analysis tools to detect unsafe coding patterns. If immediate code changes are not feasible, consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the vulnerable endpoint. Monitor logs for unusual activity indicative of exploitation attempts. Additionally, maintain an incident response plan to quickly address any detected compromise. Organizations should also track updates from the software maintainers for official patches and apply them promptly once available.
Description
calculator-boilerplate v1.0 was discovered to contain a remote code execution (RCE) vulnerability via the eval function at /routes/calculator.js. This vulnerability allows attackers to execute arbitrary code via a crafted payload injected into the input field.