WP Mail Log <= 1.1.2 - Incorrect Authorization to Authenticated (Contributor+) Data Viewing and Deletion
Strategic Overview
- Status
- Patched in 1.1.3
- Affected Plugin
- WP Mail Log
- Affected Version
<= 1.1.2- CVSS
- 6.4Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2023-5644
At a glance
CVE-2023-5644 is a medium-severity Incorrect Authorization vulnerability in the WP Mail Log WordPress plugin, affecting versions <= 1.1.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.1.3; sites on affected versions should update now. Disclosed November 2023, reported by dc11.
Vulnerability Overview
The WP Mail Log plugin for WordPress is vulnerable to unauthorized modification of data due to an insufficient capability check on the check_permission() function in all versions up to, and including, 1.1.2. This makes it possible for authenticated attackers, with contributor-level access and above, to access REST routes that they should not have access to and delete 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-863: Incorrect Authorization
WP Mail Log <= 1.1.2 carries this weakness at check_permission(), and reaching it takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For WP Mail Log the fix is 1.1.3: builds <= 1.1.2 are affected, anything from 1.1.3 onward is not.
Remediation
Update to version 1.1.3, 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 Mail Log 1.1.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Mail Log
- 8.8CVE-2023-51410: WP Mail Log Plugin <= 1.1.2 Arbitrary File Upload
CVE-2023-51410 - 8.8CVE-2023-5645: WP Mail Log <= 1.1.2 SQL injection
CVE-2023-5645 - 8.8CVE-2022-45807: WP Mail Log <= 1.0.1 Cross-Site Request Forgery
CVE-2022-45807 - 7.2CVE-2023-5674: WP Mail Log <= 1.1.2 SQL Injection
CVE-2023-5674 - 7.2CVE-2023-3088: WP Mail Log <= 1.1.1 Stored Cross-Site Scripting
CVE-2023-3088 - 6.5CVE-2023-5672: WP Mail Log <= 1.1.2 Arbitrary File Read
CVE-2023-5672 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C