CVE-2023-6506

WP 2FA <= 2.5.0 - Insecure Direct Object Reference to Arbitrary Email Sending

2024-01-02 00:00
Ulyses Saicha

Strategic Overview

Status
Patched in 2.6.0
Affected Plugin
WP 2FA – Two-factor authentication for WordPress
Affected Version
<= 2.5.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-6506
View all WP 2FA – Two-factor authentication for WordPress vulnerabilities

At a glance

CVE-2023-6506 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP 2FA WordPress plugin, affecting versions <= 2.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 2.6.0; sites on affected versions should update now. Disclosed January 2024, reported by Ulyses Saicha.

Vulnerability Overview

The WP 2FA – Two-factor authentication for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.5.0 via the send_backup_codes_email due to missing validation on a user controlled key. This makes it possible for subscriber-level attackers to email arbitrary users on the site.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP 2FA <= 2.5.0 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP 2FA the fix is 2.6.0: builds <= 2.5.0 are affected, anything from 2.6.0 onward is not.

Remediation

Update to version 2.6.0, 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.6.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6506https://www.wordfence.com/threat-intel/vulnerabilities/id/caff9be6-4161-47a0-ba47-6c8fc0c4ab40https://nvd.nist.gov/vuln/detail/CVE-2023-6506

Related records

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