Skip to main content
VulnerabilityPublished

CVE-2025-57247: Improper Access Control

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% 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:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2025

  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 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately audit their smart contracts for similar access control weaknesses, especially in whitelist and privileged function implementations. Specifically, the setColdWhiteList() and setSpecialAddress() functions should be restricted using access control modifiers such as 'onlyOwner' or role-based access control (RBAC) patterns to ensure only authorized entities can invoke them. Implementing OpenZeppelin's AccessControl or Ownable contracts can provide standardized and tested access control mechanisms. Conduct thorough testing and formal verification of smart contracts before deployment to detect such vulnerabilities. If the BATBToken contract is already deployed, consider deploying a patched version with corrected access controls and migrating users to the new contract. Additionally, monitor blockchain transactions for suspicious calls to these functions and set up alerts for unauthorized whitelist modifications. Engage with blockchain security auditors to perform comprehensive reviews. Finally, educate development teams on secure smart contract coding practices and the importance of restricting sensitive functions to prevent privilege escalation.

Description

The BATBToken smart contract (address 0xfbf1388408670c02f0dbbb74251d8ded1d63b7a2, Compiler Version v0.8.26+commit.8a97fa7a) contains incorrect access control implementation in whitelist management functions. The setColdWhiteList() and setSpecialAddress() functions in the base ERC20 contract are declared as public without proper access control modifiers, allowing any user to bypass transfer restrictions and manipulate special address settings. This enables unauthorized users to circumvent cold time transfer restrictions and potentially disrupt dividend distribution mechanisms, leading to privilege escalation and violation of the contract's intended tokenomics.

References

Community reviews

Loading reviews…