miniOrange's Google Authenticator <= 5.6.1 - Cross-Site Request Forgery to Malware Scan Termination

2022-11-01 00:00
Anonymous

Strategic Overview

Status
Patched in 5.6.2
Affected Plugin
miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator)
Affected Version
<= 5.6.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the miniOrange 2FA WordPress plugin, affecting versions <= 5.6.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.6.2; sites on affected versions should update now. Disclosed November 2022.

Vulnerability Overview

The miniOrange's Google Authenticator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.6.1. This is due to missing or incorrect nonce validation on the mo_wpns_stop_scan function. This makes it possible for unauthenticated attackers to terminate malware scans, via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in miniOrange 2FA <= 5.6.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For miniOrange 2FA the fix is 5.6.2: builds <= 5.6.1 are affected, anything from 5.6.2 onward is not.

Remediation

Update to version 5.6.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to miniOrange 2FA: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: miniOrange 2FA 5.6.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/ed117fb8-c13a-4088-aa33-8d44fc5dcf37

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C