CVE-2024-51427: Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% 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 30 Oct 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-51427, organizations should immediately audit the PepeGxng smart contract code, focusing on the mint function to identify and eliminate unsafe code execution paths. Access controls must be enforced to restrict mint function calls to authorized entities only, such as implementing role-based permissions or multisignature requirements. Deploy updated contract versions with hardened security measures, including input validation, proper authorization checks, and use of established secure coding patterns for smart contracts. Consider using formal verification tools to prove the absence of code injection vulnerabilities. Monitor blockchain activity for unusual minting transactions and set up alerting mechanisms. Users and platforms should avoid interacting with the vulnerable contract until a secure patch is released. Additionally, educating developers on secure smart contract design and conducting regular security assessments can prevent similar vulnerabilities in future deployments.
Description
An issue in the PepeGxng smart contract (which can be run on the Ethereum blockchain) allows remote attackers to have an unspecified impact via the mint function. NOTE: this is disputed by third parties because the impact is limited to function calls.