CVE-2025-57247

The BATBToken smart contract (address 0xfbf1388408670c02f0dbbb74251d8ded1d63b7a2, Compiler Version v0.8.26+commit.8a97fa7a) contains incorrect access control…

Critical · published October 6, 2025

CVSS v3.1
9.1
EPSS
0%
Percentile
28.4
In the wild
Unconfirmed
What it is

🚨 An open door for chaos! The BATBToken smart contract has a critical access control blunder that lets anyone tinker with whitelist settings. 🔥 Think of it like a bank vault where anyone can walk in and change the combination—suddenly, all your precious assets are at risk. This vulnerability allows unauthorized users to bypass established transfer restrictions and wreak havoc on the tokenomics. An attacker could potentially manipulate whitelist settings and evade cold time transfer restrictions, disrupting dividend distributions and escalating their privileges within the contract. If left unchecked, this could lead to a dramatic collapse in trust and value for the token, as the very essence of its intended financial model unravels!

Put simply

Think of it like a bank vault where anyone can walk in and change the combination—suddenly, all your precious assets are at risk. This vulnerability allows unauthorized users to bypass established transfer restrictions and wreak havoc on the tokenomics. The BATBToken smart contract improperly exposes the setColdWhiteList() and setSpecialAddress() functions as public without robust access control, allowing any user to alter key settings and permissions.

What to do

An attacker could potentially manipulate whitelist settings and evade cold time transfer restrictions, disrupting dividend distributions and escalating their privileges within the contract. If left unchecked, this could lead to a dramatic collapse in trust and value for the token, as the very essence of its intended financial model unravels! Immediate action is crucial! Implement access control modifiers for the affected functions to ensure that only authorized users can change whitelist configurations. Patch the contract to the latest secure version and conduct a thorough audit of other potential vulnerabilities in the system. You've got this! With these steps, you can restore security to your smart contract and protect its integrity. 🛡️

The record
Technical detail
CVSS v3.1
9.1 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00359 · 28.4th percentile
Published
2025-10-06T00:00Z
EPSS history
Timeline
  • 06 OCT 00:00Z
    The BATBToken smart contract (address 0xfbf1388408670c02f0dbbb74251d8ded1d63b7a2, Compiler Version v0.8.26+commit.8a97fa7a) contains incorrect access control…
    cvelistv5