# CVE-2026-14204: Google Authenticator < 0.56 - 2FA Secret Overwrite via CSRF

> Attackers can trick logged-in users into overwriting their 2FA secret, locking them out of their accounts via CSRF in the Google Authenticator plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-5j77-9g8f-r5r2

## What is CVE-2026-14204?

CVE-2026-14204 is a medium-severity vulnerability in Unknown Google Authenticator, published on 6 Aug 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

The Google Authenticator WordPress plugin before 0.56 does not verify a CSRF nonce when saving its two-factor setup, allowing attackers to trick a logged-in user into overwriting their own 2FA secret with an attacker-controlled value, which enables two-factor authentication and locks the victim out of their account.

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

## Which versions are affected by CVE-2026-14204?


## How do I fix CVE-2026-14204?

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

## Is CVE-2026-14204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14204 is a medium-severity vulnerability in Unknown Google Authenticator, published on 6 Aug 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-14204 exists.

Affected product: Unknown Google Authenticator. 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-14204/ (Markdown: https://insights.sbomify.com/CVE-2026-14204/index.md)
```

## Sources

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

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