WP-Recall – Registration, Profile, Commerce & More <= 16.26.5 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Patched in 16.26.6
- Affected Plugin
- WP-Recall – Registration, Profile, Commerce & More
- Affected Version
<= 16.26.5- CVSS
- 10.0Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2024-32709
At a glance
CVE-2024-32709 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.5. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 16.26.6; sites on affected versions should update now. Disclosed April 2024, reported by LVT-tholv2k.
Vulnerability Overview
The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 16.26.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WP-Recall <= 16.26.5 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. 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?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-Recall 16.26.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP-Recall – Registration, Profile, Commerce & More
- 9.8CVE-2024-8292: WP-Recall – Registration, Profile, Commerce & More IDOR
CVE-2024-8292 - 8.8CVE-2025-47653: WP-Recall <= 16.26.14 Local File Inclusion
CVE-2025-47653 - 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
- 5.3CVE-2025-49991: WP-Recall <= 16.26.14 Missing Authorization
CVE-2025-49991 - 5.3CVE-2024-1175: WP-Recall Payment Deletion
CVE-2024-1175
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C