Radar sectionsDatabase
Check my site
WordPress plugin

Login With OTP Over SMS, Email, WhatsApp and Google Authenticator <= 1.0.4 — Cross-Site Request Forgery to Cross-Site Scripting

CVE-2022-0875Published · Updated

Action summary

Affected: ≤1.0.4Update to 1.0.5 or newer

All remediation steps
Severity
Critical9.6
CVSS
9.6
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:C Scope
Changed
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-352 CSRF
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Login with TOTP (Google Authenticator, Microsoft Authenticator) miniorange-google-authenticator

  1. Affected≤ 1.0.4
  2. Patched in1.0.5

Update to 1.0.5 or newer.

You are affected if you run ≤ 1.0.4. Version 1.0.5 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Login with TOTP (Google Authenticator, Microsoft Authenticator).
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.0.5, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Login with TOTP (Google Authenticator, Microsoft Authenticator) to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Niraj Mahajan.

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

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Login with TOTP (Google Authenticator, Microsoft Authenticator)

All 2
More vulnerabilities in Login with TOTP (Google Authenticator, Microsoft Authenticator)
SeverityVulnerabilityCVEPublished
Medium4.8Cross-Site Scripting
≤1.0.7Update to 1.0.8
CVE-2022-1994

Same weakness (CSRF)

All CSRF
Other CSRF vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity critical, CVSS 9.6

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?