Account lockout via nonce-free 2FA secret overwrite
Published Aug 6, 2026 · Updated Aug 6, 2026
CSRF in the Google Authenticator WordPress plugin before 0.56 allows remote attackers to replace a logged-in user's 2FA secret. The save_submitted_setup_page() handler accepts attacker-chosen GA_secret and GA_otp_code values without verifying a CSRF nonce, then writes the secret and enables 2FA. Exploitation requires a logged-in user with dashboard access to load an attacker-controlled page; the attacker can control the OTP needed for login and lock the user out.
Summary
What happened
CSRF in the Google Authenticator WordPress plugin before 0.56 allows remote attackers to replace a logged-in user's 2FA secret. The save_submitted_setup_page() handler accepts attacker-chosen GA_secret and GA_otp_code values without verifying a CSRF nonce, then writes the secret and enables 2FA. Exploitation requires a logged-in user with dashboard access to load an attacker-controlled page; the attacker can control the OTP needed for login and lock the user out.
The record
- CVE
- CVE-2026-14204
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Go standard library
- Product
- Google Authenticator
- Classifications
- CWE-352, T1531
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.56
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- WPScan auto-submitting CSRF proof of conceptfunctional · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo