Bulk Posts Editing For WordPress <= 4.2.3 - Authenticated (Subscriber+) Missing Authorization
Strategic Overview
- Status
- Patched in 4.2.4
- Affected Plugin
- WBULKiT – Bulk Edit Posts & Pages
- Affected Version
<= 4.2.3- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-4199
At a glance
CVE-2024-4199 is a medium-severity Missing Authorization vulnerability in the WBULKiT WordPress plugin, affecting versions <= 4.2.3. 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 4.2.4; sites on affected versions should update now. Disclosed May 2024, reported by Benedictus Jovan (aillesiM).
Vulnerability Overview
The Bulk Posts Editing For WordPress plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on the plugin's AJAX actions in all versions up to, and including, 4.2.3. This makes it possible for authenticated attackers, with subscriber access and higher, to invoke their corresponding functions. This may lead to post creation and duplication, post content retrieval, post taxonomy manipulation.
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
Reaching this weakness in WBULKiT <= 4.2.3 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 WBULKiT the fix is 4.2.4: builds <= 4.2.3 are affected, anything from 4.2.4 onward is not.
Remediation
Update to version 4.2.4, 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: WBULKiT 4.2.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WBULKiT – Bulk Edit Posts & Pages
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C