Google Authenticator
Approved changes feed: RSS · Atom
cpe:2.3:a:unknown:google_authenticator:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Unknown (668ca391-a6cc-5e33-879b-83885214de33) |
|---|---|
| Product | Google Authenticator (767dd6b9-d33a-5e28-b450-abfd0d2960d2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-14204 |
vulnerable | 2026-09-16 04:33:12.156607 |
Google Authenticator < 0.56 - 2FA Secret Overwrite via CSRF
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.
Published: 2026-08-06T06:00:13.328Z
Updated: 2026-08-06T15:31:31.455Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-0875 |
vulnerable | 2026-06-08 05:39:11.394510 |
miniOrange Google Authenticator < 1.0.5 - CSRF to Stored Cross-Site Scripting
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
Published: 2022-06-27T08:55:54.000Z
Updated: 2024-08-02T23:40:04.480Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.