WP-Recall – Registration, Profile, Commerce & More <= 16.26.5 - Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 16.26.6
- Affected Plugin
- WP-Recall – Registration, Profile, Commerce & More
- Affected Version
<= 16.26.5- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-32604
At a glance
CVE-2024-32604 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 16.26.6; sites on affected versions should update now. Disclosed April 2024, reported by Kyle Sanchez.
Vulnerability Overview
The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 16.26.5 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to retrieve other users chat messages.
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-Recall <= 16.26.5 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-Recall the fix is 16.26.6: builds <= 16.26.5 are affected, anything from 16.26.6 onward is not.
Remediation
Update to version 16.26.6, 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-Recall 16.26.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP-Recall – Registration, Profile, Commerce & More
- 10.0CVE-2024-32709: WP-Recall SQL Injection
CVE-2024-32709 - 9.9CVE-2024-32710: WP-Recall SQL Injection
CVE-2024-32710 - 8.8CVE-2025-47653: WP-Recall <= 16.26.14 Local File Inclusion
CVE-2025-47653 - 7.5CVE-2025-1323: WP-Recall SQL Injection
CVE-2025-1323 - 6.4CVE-2025-1324: WP-Recall Stored XSS
CVE-2025-1324 - 6.3CVE-2025-1325: WP-Recall Authenticated (Subscriber+) Arbitrary
CVE-2025-1325 - 6.1CVE-2025-52796: WP-Recall <= 16.26.14 Reflected Cross-Site Scripting
CVE-2025-52796 - 6.1WP-Recall <= 16.24.47 Reflected Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C