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-2025-14904: CWE-352 Cross-Site Request Forgery (CSRF) in anilankola Newsletter Email Subscribe

0
Medium
VulnerabilityCVE-2025-14904cvecve-2025-14904cwe-352
Published: Wed Jan 07 2026 (01/07/2026, 06:35:57 UTC)
Source: CVE Database V5
Vendor/Project: anilankola
Product: Newsletter Email Subscribe

Description

The Newsletter Email Subscribe plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4. This is due to incorrect nonce validation on the nels_settings_page function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 01/07/2026, 07:07:06 UTC

Technical Analysis

CVE-2025-14904 is a medium-severity CSRF vulnerability identified in the Newsletter Email Subscribe plugin for WordPress, maintained by anilankola. The vulnerability stems from incorrect nonce validation within the nels_settings_page function, which is responsible for handling plugin settings updates. Nonces are security tokens used to verify the legitimacy of requests and prevent CSRF attacks. Due to improper validation, an attacker can craft a malicious request that, when executed by an authenticated administrator (via clicking a link or visiting a crafted webpage), causes unauthorized changes to the plugin’s configuration. This attack does not require the attacker to be authenticated but does require user interaction from a privileged user, making it a targeted threat. The vulnerability affects all versions up to and including 2.4 of the plugin. The CVSS v3.1 base score is 4.3, reflecting a network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, limited integrity impact, and no availability impact. No public exploits have been reported yet, but the vulnerability could be leveraged to alter plugin behavior, potentially enabling further attacks or disrupting newsletter subscription processes. The plugin is widely used in WordPress environments, which are prevalent across many European organizations, especially in SMBs and content-driven websites.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the integrity of WordPress plugin configurations. Unauthorized changes to the Newsletter Email Subscribe plugin settings could lead to manipulation of newsletter subscription processes, potentially enabling spam campaigns, phishing distribution, or disruption of legitimate communications. While confidentiality and availability are not directly impacted, the integrity compromise could erode trust in organizational communications and lead to reputational damage. Organizations with WordPress sites managed by administrators susceptible to phishing or social engineering are particularly vulnerable. Given the widespread use of WordPress in Europe, especially in countries with high digital adoption like Germany, the UK, France, and the Netherlands, the threat could affect a significant number of websites. Attackers might exploit this vulnerability as a foothold for more complex attacks or to spread misinformation via newsletters.

Mitigation Recommendations

1. Monitor the plugin vendor’s official channels for security patches and apply updates promptly once available. 2. Until patches are released, implement Web Application Firewall (WAF) rules to detect and block suspicious POST requests targeting the plugin’s settings endpoints. 3. Educate WordPress administrators about the risks of phishing and social engineering, emphasizing caution when clicking links from untrusted sources. 4. Enforce multi-factor authentication (MFA) for WordPress admin accounts to reduce the risk of account compromise. 5. Review and harden WordPress security configurations, including limiting administrative access and using security plugins that can detect anomalous configuration changes. 6. Consider temporarily disabling or replacing the Newsletter Email Subscribe plugin if it is not critical, to eliminate exposure until a fix is available. 7. Regularly audit plugin settings and logs for unauthorized changes to detect potential exploitation early.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-18T18:04:39.071Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695e0294a55ed4ed9984d56f

Added to database: 1/7/2026, 6:52:04 AM

Last enriched: 1/7/2026, 7:07:06 AM

Last updated: 1/8/2026, 9:16:08 AM

Views: 8

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