Strategic Overview
- Status
- Patched in 4.8
- Affected Plugin
- WP-Chatbot for Messenger
- Affected Version
<= 4.7- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-32581
At a glance
CVE-2023-32581 is a medium-severity Missing Authorization vulnerability in the WP-Chatbot for Messenger WordPress plugin, affecting versions <= 4.7. It carries a CVSS score of 5.4 (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 4.8; sites on affected versions should update now. Disclosed May 2023, reported by István Márton.
Vulnerability Overview
The WP-Chatbot for Messenger plugin for WordPress is vulnerable to unauthorized access and modification of data due to missing capability checks on several functions like csv(), cancel_subscribe(), create_subscribe(), notice_lead_off(), banner_off() and many more called via AJAX actions in versions up to, and including, 4.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify the plugin's settings, manipulate subscription settings, and export submitted form 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
WP-Chatbot for Messenger <= 4.7 carries this weakness at cancel_subscribe(), 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-Chatbot for Messenger the fix is 4.8: builds <= 4.7 are affected, anything from 4.8 onward is not.
Remediation
Update to version 4.8, 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-Chatbot for Messenger 4.8 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