StopBadBots <= 7.23 - Missing Authorization to Arbitrary Plugin Installation
Strategic Overview
- Status
- Patched in 7.24
- Affected Version
<= 7.23- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-3883
At a glance
CVE-2022-3883 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 <= 7.23. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 7.24; sites on affected versions should update now. Disclosed November 2022, reported by István Márton.
Vulnerability Overview
The StopBadBots plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the stopbadbots_install_plugin() function in versions up to, and including, 7.23. This makes it possible for authenticated attackers with minimal permission, such as a subscriber, to install arbitrary plugins on the vulnerable site. This could be used to install additional vulnerable plugins that could aid in further compromise of the site.
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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection <= 7.23 carries this weakness at stopbadbots_install_plugin(), 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 7.24: builds <= 7.23 are affected, anything from 7.24 onward is not.
Remediation
Update to version 7.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 7.24 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 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