HomeWordPress vulnerabilitiesGoogle Authenticator
Google Authenticator vulnerabilities
Google Authenticator has 5 known vulnerabilities in this database. The most recent published record is dated 6 Aug 2026.
- Known vulnerabilities
- 5
- Active installs
- 20,000+
- Latest version
- 0.56
- Last updated
- 23 Aug 2026
- Most recent
- 6 Aug 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2026-14204 | Medium 6.5 | Before 0.56 | Fixed in 0.56 | 6 Aug 2026 |
| Broken access control CVE-2022-4943 | High 7.5 | Up to 5.6.5 | No fixed version yet | 20 Oct 2023 |
| Cross-site scripting (XSS) CVE-2022-0875 | Medium 4.3 | Before 1.0.5 | Fixed in 1.0.5 | 27 Jun 2022 |
| Cross-site scripting (XSS) CVE-2022-1321 | Medium 4.8 | Before 5.5.6 | Fixed in 5.5.6 | 27 Jun 2022 |
| Cross-site request forgery (CSRF) CVE-2022-0229 | High 8.1 | Before 5.5 | Fixed in 5.5 | 21 Mar 2022 |
Read the published descriptions
- CVE-2026-14204, 6 Aug 2026
- 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. CVE record
- CVE-2022-4943, 20 Oct 2023
- The miniOrange's Google Authenticator plugin for WordPress is vulnerable to authorization bypass due to a missing capability check when changing plugin settings in versions up to, and including, 5.6.5. This makes it possible for unauthenticated attackers to change the plugin's settings. CVE record
- CVE-2022-0875, 27 Jun 2022
- The Google Authenticator WordPress plugin before 1.0.5 does not have CSRF check when saving its settings, and does not sanitise as well as escape them, allowing attackers to make a logged in admin change them and perform Cross-Site Scripting attacks CVE record
- CVE-2022-1321, 27 Jun 2022
- The miniOrange's Google Authenticator WordPress plugin before 5.5.6 does not sanitise and escape some of its settings, leading to malicious users with administrator privileges to store malicious Javascript code leading to Cross-Site Scripting attacks when unfiltered_html is disallowed (for example in multisite setup) CVE record
- CVE-2022-0229, 21 Mar 2022
- The miniOrange's Google Authenticator WordPress plugin before 5.5 does not have proper authorisation and CSRF checks when handling the reconfigureMethod, and does not validate the parameters passed to it properly. As a result, unauthenticated users could delete arbitrary options from the blog, making it unusable. CVE record
What to do if you run Google Authenticator
If you run Google Authenticator, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Google Authenticator vulnerabilities
Free. We email you when a new vulnerability is published for Google Authenticator, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.