Skip to main content
CVE-2024-51425VulnerabilityPublished Updated

CVE-2024-51425: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

AI-suggested

1. Conduct a thorough audit of the WaterToken smart contract’s authorization logic to identify and restrict unauthorized function calls. 2. Implement role-based access control (RBAC) or multi-signature requirements for sensitive functions to reduce risk of misuse. 3. If possible, deploy an upgraded version of the contract with corrected authorization checks and migrate token holders to the new contract. 4. Monitor blockchain transactions involving WaterToken for suspicious activity indicative of exploitation attempts. 5. Limit privileges granted to external users or contracts interacting with WaterToken to the minimum necessary. 6. Engage with blockchain security experts to perform penetration testing and formal verification of smart contract code. 7. Inform stakeholders and users about the vulnerability and encourage caution in interacting with WaterToken until mitigations are in place. 8. Consider using smart contract upgradeability patterns or proxy contracts to allow patching vulnerabilities in the future.

Description

An issue in the WaterToken smart contract (which can be run on the Ethereum blockchain) allows remote attackers to have an unspecified impact. NOTE: this is disputed by third parties because the impact is limited to function calls.

References

Community reviews

Loading reviews…