# CVE-2025-57247: The BATBToken smart contract (address 0xfbf1388408670c02f0dbbb74251d8ded1d63b7a2, Compiler Version v0.8.26+commit.8a97fa7a) contains incorre


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-h4cr-6c88-hv52

## What is CVE-2025-57247?

CVE-2025-57247 is a critical vulnerability in n/a, published on 6 Oct 2025. 

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-57247?


## How do I fix CVE-2025-57247?

No fix has been published for CVE-2025-57247 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-57247 being exploited?

There is no known exploitation of CVE-2025-57247 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57247 and fix it if it is affected.

What it is: CVE-2025-57247 is a critical vulnerability in n/a, published on 6 Oct 2025. 
Exploitation: There is no known exploitation of CVE-2025-57247 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-57247/ (Markdown: https://insights.sbomify.com/CVE-2025-57247/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57247
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57247
- OSV: https://osv.dev/vulnerability/CVE-2025-57247

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-57247/
Summaries are generated and may contain mistakes; the official description above is the record.