Newsletter - API v1 and v2 addon for Newsletter <= 2.4.5 - Missing Authorization to Email Subscribers Management
Strategic Overview
- Status
- Patched in 2.4.6
- Affected Plugin
- Newsletter - API v1 and v2 addon for Newsletter
- Affected Version
<= 2.4.5- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-5674
At a glance
CVE-2024-5674 is a medium-severity Missing Authorization vulnerability in the Newsletter - API v1 and v2 addon for Newsletter WordPress plugin, affecting versions <= 2.4.5. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.6; sites on affected versions should update now. Disclosed June 2024, reported by Arkadiusz Hydzik.
Vulnerability Overview
The Newsletter - API v1 and v2 addon plugin for WordPress is vulnerable to unauthorized subscribers management due to PHP type juggling issue on the check_api_key function in all versions up to, and including, 2.4.5. This makes it possible for unauthenticated attackers to list, create or delete newsletter subscribers. This issue affects only sites running the PHP version below 8.0
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Newsletter - API v1 and v2 addon for Newsletter <= 2.4.5 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 Newsletter - API v1 and v2 addon for Newsletter the fix is 2.4.6: builds <= 2.4.5 are affected, anything from 2.4.6 onward is not.
Remediation
Update to version 2.4.6, 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: Newsletter - API v1 and v2 addon for Newsletter 2.4.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C