# CVE-2025-27579: Cross-site request forgery in ESP-MIner

> Attackers can exploit CSRF to modify Bitcoin miner payout addresses and hardware settings, requiring users to upgrade firmware.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-38q3-97f6-wg52

## What is CVE-2025-27579?

CVE-2025-27579 is a medium-severity vulnerability in Bitaxe ESP-MIner, published on 2 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Bitaxe ESP-Miner before 2.5.0 with AxeOS, one can use an /api/system CSRF attack to update the payout address (aka stratumUser) for a Bitaxe Bitcoin miner, or change the frequency and voltage settings.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-27579 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27579 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27579 is a medium-severity vulnerability in Bitaxe ESP-MIner, published on 2 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27579 exists.

Affected product: Bitaxe ESP-MIner. 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-27579/ (Markdown: https://insights.sbomify.com/CVE-2025-27579/index.md)
```

## Sources

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

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