WP-Recall – Registration, Profile, Commerce & More <= 16.26.10 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Shortcode Exeuction
Strategic Overview
- Status
- Patched in 16.26.12
- Affected Plugin
- WP-Recall – Registration, Profile, Commerce & More
- Affected Version
<= 16.26.10- CVSS
- 6.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-1325
At a glance
CVE-2025-1325 is a medium-severity Missing Authorization vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.10. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 16.26.12; sites on affected versions should update now. Disclosed March 2025, reported by Krzysztof Zając.
Vulnerability Overview
The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to arbitrary shortcode execution due to a missing capability check on the 'rcl_preview_post' AJAX endpoint in all versions up to, and including, 16.26.10. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.
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
WP-Recall <= 16.26.10 carries this weakness at rcl_preview_post, and reaching it takes an account at Subscriber level or above. 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-Recall the fix is 16.26.12: builds <= 16.26.10 are affected, anything from 16.26.12 onward is not.
Remediation
Update to version 16.26.12, 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.12 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 - 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 - 7.5CVE-2025-1323: WP-Recall SQL Injection
CVE-2025-1323 - 6.4CVE-2025-1324: WP-Recall Stored XSS
CVE-2025-1324 - 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