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

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N`)
- **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 available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-x4q4-3ww4-h329

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

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-287 (Improper Authentication)

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54510 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54510 exists.

Affected product: murtaza-nasir speakr. 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-2026-54510/ (Markdown: https://insights.sbomify.com/CVE-2026-54510/index.md)
```

## Sources

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

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