Is google-authenticator (WordPress plugin) vulnerable?

WordPress google-authenticator has 5 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

5advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-42461Broken Access Control vulnerability in miniOrange's Google Authenticator plugin <= 5.6.1 on WordPress.medium5.4<5.6.25.6.2
CVE-2022-44589Exposure of Sensitive Information to an Unauthorized Actor vulnerability in miniOrange miniOrange's Google Authenticator – WordPress Two Fachigh8.1<5.6.25.6.2
CVE-2022-1321The miniOrange's Google Authenticator WordPress plugin before 5.5.6 does not sanitise and escape some of its settings, leading to malicious medium4.8<5.5.65.5.6
CVE-2022-0229The miniOrange's Google Authenticator WordPress plugin before 5.5 does not have proper authorisation and CSRF checks when handling the reconhigh8.1<5.55.5
CVE-2022-0875The Google Authenticator WordPress plugin before 1.0.5 does not have CSRF check when saving its settings, and does not sanitise as well as emedium4.3<1.0.51.0.5

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.