CVE-2024-8292

WP-Recall – Registration, Profile, Commerce & More <= 16.26.8 - Insecure Direct Object Reference to Unauthenticated Arbitrary Password Update

2024-09-05 00:00
wesley (wcraft)

Strategic Overview

Status
Patched in 16.26.9
Affected Plugin
WP-Recall – Registration, Profile, Commerce & More
Affected Version
<= 16.26.8
CVSS
9.8Critical
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-8292
View all WP-Recall – Registration, Profile, Commerce & More vulnerabilities

At a glance

CVE-2024-8292 is a critical-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.8. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 16.26.9; sites on affected versions should update now. Disclosed September 2024, reported by wesley (wcraft).

Vulnerability Overview

The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to privilege escalation/account takeover in all versions up to, and including, 16.26.8. This is due to to plugin not properly verifying a user's identity during new order creation. This makes it possible for unauthenticated attackers to supply any email through the user_email field and update the password for that user during new order creation. This requires the commerce addon to be enabled in order to exploit.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP-Recall <= 16.26.8 takes no account at all. 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-Recall the fix is 16.26.9: builds <= 16.26.8 are affected, anything from 16.26.9 onward is not.

Remediation

Update to version 16.26.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP-Recall 16.26.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-8292https://www.wordfence.com/threat-intel/vulnerabilities/id/8fa4b5df-dc71-49de-880b-895eb1d9cdcahttps://nvd.nist.gov/vuln/detail/CVE-2024-8292

Related records

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