CVE-2024-51424: Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 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-51424, organizations should immediately audit all instances of the PepeGxng smart contract in their environment and any dependent systems. Restrict access to the Owned.setOwner function by implementing strict access control mechanisms, such as role-based permissions or multi-signature requirements, to prevent unauthorized calls. Where possible, redeploy updated versions of the contract with corrected ownership management logic that enforces proper authentication and authorization checks. Employ runtime monitoring tools to detect anomalous transactions or ownership changes on the blockchain. Engage with the smart contract developers or community to obtain or contribute patches addressing this vulnerability. Additionally, consider using formal verification tools to validate smart contract logic and prevent similar vulnerabilities. For critical assets, implement off-chain controls and insurance mechanisms to mitigate financial risks. Educate developers and auditors on secure smart contract design principles, emphasizing the importance of access control and ownership validation.
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 Owned.setOwner function. NOTE: this is disputed by third parties because the impact is limited to function calls.