Swift Performance Lite <= 2.3.6.18 - Incorrect Authorization to Authenticated (Subscriber+) Settings Modification
Strategic Overview
- Status
- Patched in 2.3.6.19
- Affected Plugin
- Swift Performance Lite
- Affected Version
<= 2.3.6.18- CVSS
- 5.4Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2024-3722
At a glance
CVE-2024-3722 is a medium-severity Incorrect Authorization vulnerability in the Swift Performance Lite WordPress plugin, affecting versions <= 2.3.6.18. It carries a CVSS score of 5.4 (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.6.19; sites on affected versions should update now. Disclosed May 2024, reported by Lucio Sá.
Vulnerability Overview
The Swift Performance Lite plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the ajax_handler() function in all versions up to, and including, 2.3.6.18. This makes it possible for authenticated attackers, with subscriber-level access and above, to retrieve and modify settings.
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-863: Incorrect Authorization
Swift Performance Lite <= 2.3.6.18 carries this weakness at ajax_handler(), and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Swift Performance Lite the fix is 2.3.6.19: builds <= 2.3.6.18 are affected, anything from 2.3.6.19 onward is not.
Remediation
Update to version 2.3.6.19, 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: Swift Performance Lite 2.3.6.19 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C