CVE-2026-54510 Speakr: CSRF bypass via unauthenticated API token parameter in csrf_exempt_for_api_tokens hook
Attackers can bypass CSRF protection and authentication checks to modify user profiles, settings, and gain admin privileges in Speakr.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-54510?
CVE-2026-54510 is a high-severity vulnerability in murtaza-nasir speakr, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Which versions are affected by CVE-2026-54510?
How do I fix CVE-2026-54510?
No fix has been published for CVE-2026-54510 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-54510 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54510 exists.
Sources
Also known as GHSA-x4q4-3ww4-h329.