CVE-2024-51426: Incorrect Authorization
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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: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-51426, organizations should first conduct a thorough security audit of the PepeGxng smart contract, focusing on the _transfer function and related authorization mechanisms. Implement strict access controls to ensure only authorized entities can invoke sensitive functions. Employ role-based permissions and multi-signature requirements where feasible to reduce the risk of unauthorized transfers. Monitor blockchain transactions involving PepeGxng tokens for unusual patterns indicative of exploitation attempts. Engage with the contract developers or community to advocate for an official patch or contract upgrade that addresses the authorization flaw. Until a fix is available, consider limiting exposure by restricting token usage in critical applications or migrating assets to more secure contracts. Use blockchain analytics tools to track and respond to suspicious activities promptly. Educate users and stakeholders about the risk and encourage vigilance when interacting with the PepeGxng token. Finally, maintain up-to-date incident response plans tailored to smart contract vulnerabilities and blockchain-specific threats.
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 _transfer function. NOTE: this is disputed by third parties because the impact is limited to function calls.