Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-5674: CWE-862 Missing Authorization in The Newsletter Team Newsletter - API v1 and v2 addon for Newsletter

0
Medium
VulnerabilityCVE-2024-5674cvecve-2024-5674cwe-862
Published: Wed Jun 12 2024 (06/12/2024, 11:05:09 UTC)
Source: CVE Database V5
Vendor/Project: The Newsletter Team
Product: Newsletter - API v1 and v2 addon for Newsletter

Description

CVE-2024-5674 is a medium-severity vulnerability in The Newsletter Team's Newsletter - API v1 and v2 addon for WordPress, affecting all versions up to 2. 4. 5 when running on PHP versions below 8. 0. Due to a PHP type juggling issue in the check_api_key function, unauthenticated attackers can bypass authorization controls and manage newsletter subscribers, including listing, creating, or deleting them. The vulnerability does not require user interaction or authentication and can be exploited remotely over the network. Although no known exploits are currently reported in the wild, the flaw poses a risk to the confidentiality and integrity of subscriber data. Organizations using this plugin on vulnerable PHP versions should prioritize upgrading PHP or applying patches once available. This vulnerability primarily impacts WordPress sites globally that use this plugin and older PHP versions, with particular risk in countries where WordPress market share is high and PHP 7. x remains common.

AI-Powered Analysis

AILast updated: 02/26/2026, 02:46:23 UTC

Technical Analysis

CVE-2024-5674 is a vulnerability classified under CWE-862 (Missing Authorization) found in The Newsletter Team's Newsletter - API v1 and v2 addon plugin for WordPress. The root cause is a PHP type juggling issue within the check_api_key function, which improperly validates API keys due to weak type comparisons. This flaw allows unauthenticated remote attackers to bypass authorization checks and perform subscriber management operations such as listing, creating, or deleting newsletter subscribers. The vulnerability affects all versions of the plugin up to and including 2.4.5 but only on systems running PHP versions below 8.0, as PHP 8.0 and above have stricter type handling that mitigates this issue. The attack vector is network-based with no privileges or user interaction required, making exploitation relatively straightforward. The impact primarily compromises confidentiality and integrity of subscriber data but does not affect availability. No public exploits have been reported yet, but the vulnerability is rated with a CVSS 3.1 base score of 6.5 (medium severity), reflecting its moderate risk. Organizations using this plugin should monitor for patches and consider upgrading PHP to version 8.0 or higher to mitigate the vulnerability.

Potential Impact

The vulnerability allows unauthorized attackers to access and manipulate newsletter subscriber data without authentication, leading to potential data leakage, subscriber list tampering, and disruption of newsletter communications. Confidential subscriber information could be exposed or altered, undermining trust and potentially violating privacy regulations such as GDPR. Integrity of subscriber lists can be compromised by unauthorized additions or deletions, which may affect marketing campaigns and customer engagement. Although availability is not directly impacted, the unauthorized control over subscriber data could indirectly disrupt business operations reliant on accurate mailing lists. Organizations with large subscriber bases or those in regulated industries face heightened risks. The ease of exploitation and network accessibility increase the likelihood of attacks, especially on sites running outdated PHP versions. This could lead to reputational damage, legal consequences, and financial losses if exploited at scale.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately verify the PHP version running on their WordPress servers and upgrade to PHP 8.0 or later, as this resolves the underlying type juggling issue. If upgrading PHP is not immediately feasible, administrators should disable or restrict access to the Newsletter - API v1 and v2 addon until a vendor patch is released. Monitoring and logging API access attempts can help detect suspicious activity related to subscriber management. Applying web application firewall (WAF) rules to block unauthorized API requests targeting the newsletter endpoints can provide temporary protection. Organizations should also ensure that the Newsletter plugin and its addons are kept up to date with the latest security patches once available. Conducting regular security audits and penetration testing focused on API authorization controls will help identify similar weaknesses. Finally, limiting API exposure to trusted IP addresses or VPNs can reduce the attack surface.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-06-06T08:37:46.311Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6befb7ef31ef0b55cc74

Added to database: 2/25/2026, 9:38:55 PM

Last enriched: 2/26/2026, 2:46:23 AM

Last updated: 2/26/2026, 8:04:42 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats