CVE-2022-44595

WP 2FA – Two-factor authentication for WordPress <= 2.2.0 - Missing Authorization

2022-12-07 00:00
Calvin Alkan

Strategic Overview

Status
Patched in 2.2.1
Affected Plugin
WP 2FA – Two-factor authentication for WordPress
Affected Version
<= 2.2.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-44595
View all WP 2FA – Two-factor authentication for WordPress vulnerabilities

At a glance

CVE-2022-44595 is a medium-severity Missing Authorization vulnerability in the WP 2FA WordPress plugin, affecting versions <= 2.2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed December 2022, reported by Calvin Alkan.

Vulnerability Overview

The WP 2FA plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the login_form_validate_2fa function in versions up to, and including, 2.2.0. This makes it possible for authenticated attackers to receive a 2fa login code even if the provider is not enabled for that user.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WP 2FA <= 2.2.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP 2FA the fix is 2.2.1: builds <= 2.2.0 are affected, anything from 2.2.1 onward is not.

Remediation

Update to version 2.2.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP 2FA 2.2.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-44595https://www.wordfence.com/threat-intel/vulnerabilities/id/1c51a3f8-dee1-4744-8353-864312c89021https://nvd.nist.gov/vuln/detail/CVE-2022-44595

Related records

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