CVE-2024-39001: ag-grid-enterprise · Prototype Pollution
Source CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 1 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
- Upgrade ag-grid-enterprise to a version where this vulnerability is patched once available. Monitor vendor advisories for official patches.
- Implement strict input validation and sanitization to prevent injection of malicious properties into JSON or JavaScript objects.
- Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in web applications using ag-grid.
- Restrict privileges and access controls to minimize the ability of attackers to reach the required privilege level for exploitation.
- Conduct thorough code reviews and security testing focusing on prototype pollution and object manipulation vulnerabilities.
- Use runtime application self-protection (RASP) or web application firewalls (WAF) with rules targeting prototype pollution attack patterns.
- Monitor application logs and behavior for anomalies indicative of prototype pollution exploitation attempts.
- Educate developers on secure coding practices related to JavaScript object handling and prototype pollution risks.
Description
ag-grid-enterprise v31.3.2 was discovered to contain a prototype pollution via the component _ModuleSupport.jsonApply. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.