CVE-2024-5674: CWE-862 Missing Authorization in The Newsletter Team Newsletter - API v1 and v2 addon for Newsletter
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 Analysis
Technical Summary
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.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Brazil, Netherlands, Italy, Spain
CVE-2024-5674: CWE-862 Missing Authorization in The Newsletter Team 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
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.
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 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25191: Uncontrolled Search Path Element in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-23703: Incorrect default permissions in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-1311: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in bearsthemes Worry Proof Backup
HighFinding Signal in the Noise: Lessons Learned Running a Honeypot with AI Assistance [Guest Diary], (Tue, Feb 24th)
MediumCVE-2026-2506: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in motahar1 EM Cost Calculator
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.