All Users Messenger <= 1.24 - Authenticated (Subscriber+) Insecure Direct Object Reference to Message Deletion
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- All Users Messenger
- Affected Version
<= 1.24- CVSS
- 5.4Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-4023
At a glance
CVE-2023-4023 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the All Users Messenger WordPress plugin, affecting versions <= 1.24. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2023, reported by Dmitrii Ignatyev.
Vulnerability Overview
The All Users Messenger plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 1.24 due to missing validation on a user controlled key. This can allow authenticated attackers with subscriber access to delete arbitrary messages.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in All Users Messenger <= 1.24 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for All Users Messenger yet, so installs running <= 1.24 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C