CVE-2024-36575: getsetprop · Code Injection
Affects getsetpropSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:08 UTC
- 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.
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 17 Jun 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmgetsetproppkg:npm/getsetpropOther 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
To mitigate CVE-2024-36575, organizations should immediately audit their software dependencies to identify usage of getsetprop 1.1.0 and upgrade to a patched version once available. In the absence of an official patch, consider temporarily removing or replacing the vulnerable library with a secure alternative. Implement strict input validation and sanitization to prevent prototype pollution attacks. Employ runtime application self-protection (RASP) and web application firewalls (WAF) configured to detect and block suspicious prototype manipulation patterns. Conduct thorough code reviews focusing on object prototype handling and global property access. Monitor application logs and network traffic for unusual behavior indicative of exploitation attempts. Educate development teams about secure coding practices related to JavaScript prototype handling. Finally, maintain an incident response plan to quickly address any detected exploitation.
Description
A Prototype Pollution issue in getsetprop 1.1.0 allows an attacker to execute arbitrary code via global.accessor.