Google Authenticator < 0.56 - 2FA Secret Overwrite via CSRF
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-352.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Google Authenticator | before 0.56 | 0.56 | Patch available | CNA |
- Google Authenticator VendorUnknown Affected before 0.56 Fixed in 0.56 Patch available CNA
Remediation
- Fix · CNA Google Authenticator (Unknown) Fixed in 0.56
Timeline
- 2026-10-02 Threatist record created from CVE-2026-14204
- 2026-10-03 Alias added: GHSA-5j77-9g8f-r5r2
References
Sources
- CVE-2026-14204 · CVE Program
- CVE-2026-14204 · NVD
- FIRST EPSS
- GHSA-5j77-9g8f-r5r2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences