WP Tools <= 3.42 - Missing Authorization to Select Plugin Installation
Strategic Overview
- Status
- Patched in 3.43
- Affected Plugin
- WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log
- Affected Version
<= 3.42- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-3881
At a glance
CVE-2022-3881 is a medium-severity Missing Authorization vulnerability in the WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log WordPress plugin, affecting versions <= 3.42. 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 3.43; sites on affected versions should update now. Disclosed November 2022, reported by István Márton.
Vulnerability Overview
The WP Tools plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the wptools_install_plugin() function in versions up to, and including, 3.42. This makes it possible for authenticated attackers with minimal permission, such as a subscriber, to install other plugins owned by the developer 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
WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log <= 3.42 carries this weakness at wptools_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 WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log the fix is 3.43: builds <= 3.42 are affected, anything from 3.43 onward is not.
Remediation
Update to version 3.43, 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: WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log 3.43 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 WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C