SecuPress Free <= 2.3.9 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Installation
Strategic Overview
- Status
- Patched in 2.3.10
- Affected Plugin
- SecuPress with Simple SSL – Simple and Performant Security
- Affected Version
<= 2.3.9- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-3452
At a glance
CVE-2025-3452 is a medium-severity Missing Authorization vulnerability in the SecuPress with Simple SSL WordPress plugin, affecting versions <= 2.3.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.3.10; sites on affected versions should update now. Disclosed April 2025, reported by mikemyers.
Vulnerability Overview
The SecuPress Free — WordPress Security plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'secupress_reinstall_plugins_admin_ajax_cb' function in all versions up to, and including, 2.3.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install arbitrary plugins.
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
SecuPress with Simple SSL <= 2.3.9 carries this weakness at secupress_reinstall_plugins_admin_ajax_cb, 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 SecuPress with Simple SSL the fix is 2.3.10: builds <= 2.3.9 are affected, anything from 2.3.10 onward is not.
Remediation
Update to version 2.3.10, 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: SecuPress with Simple SSL 2.3.10 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 SecuPress with Simple SSL – Simple and Performant Security
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C