Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection <= 10.23 - Missing Authorization to Information Expsoure
Strategic Overview
- Status
- Patched in 10.24
- Affected Version
<= 10.23- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-4355
At a glance
CVE-2024-4355 is a medium-severity Missing Authorization vulnerability in the Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection WordPress plugin, affecting versions <= 10.23. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 10.24; sites on affected versions should update now. Disclosed May 2024, reported by Krzysztof Zając.
Vulnerability Overview
The Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the stopbadbots_get_ajax_data() function in all versions up to, and including, 10.23. This makes it possible for authenticated attackers, with subscriber-level access and above, to expose visitor data.
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
Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection <= 10.23 carries this weakness at stopbadbots_get_ajax_data(), and reaching it takes a caller who can reach the endpoint. 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 Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection the fix is 10.24: builds <= 10.23 are affected, anything from 10.24 onward is not.
Remediation
Update to version 10.24, 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: Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection 10.24 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection
- 9.8CVE-2022-0949: WP Block and Stop Bad Bots <= 6.92 SQL Injection
CVE-2022-0949 - 9.8CVE-2021-25070: WP Block and Stop Bad Bots <= 6.88 SQL Injection
CVE-2021-25070 - 9.8CVE-2021-24863: WP Block and Stop Bad Bots Crawlers… SQL Injection
CVE-2021-24863 - 8.8CVE-2021-24727: WP Block and Stop Bad Bots Crawlers… SQL Injection
CVE-2021-24727 - 6.5CVE-2025-9376: Block Bad Bots and Stop… Insufficient Authorization
CVE-2025-9376 - 6.1Block Bad Bots and Stop Bad Bots… Reflected XSS
- 6.1Block Bad Bots and Stop Bad Bots… Reflected XSS
- 4.4CVE-2023-32496: StopBadBots <= 7.31 Stored Cross-Site Scripting
CVE-2023-32496
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C