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-10691: CWE-352 Cross-Site Request Forgery (CSRF) in yudiz Easy Email Subscription

0
Medium
VulnerabilityCVE-2025-10691cvecve-2025-10691cwe-352
Published: Thu Nov 06 2025 (11/06/2025, 03:27:01 UTC)
Source: CVE Database V5
Vendor/Project: yudiz
Product: Easy Email Subscription

Description

The Easy Email Subscription plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3. This is due to missing or incorrect nonce validation on the show_editsub_page() function. This makes it possible for unauthenticated attackers to delete arbitrary subscribers 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: 11/06/2025, 03:58:08 UTC

Technical Analysis

CVE-2025-10691 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability identified in the yudiz Easy Email Subscription plugin for WordPress, affecting all versions up to and including 1.3. The vulnerability stems from the absence or improper implementation of nonce validation in the show_editsub_page() function, which is responsible for managing subscriber edits. Nonces are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Due to this missing validation, an attacker can craft a malicious request that, when executed by an authenticated site administrator (for example, by clicking a specially crafted link), results in the deletion of arbitrary subscribers without the administrator's explicit consent. This attack does not require the attacker to be authenticated, but it does require user interaction by the administrator. The vulnerability impacts the integrity of subscriber data by enabling unauthorized deletion but does not affect confidentiality or availability. The CVSS v3.1 score of 4.3 reflects the attack vector being network-based, low attack complexity, no privileges required, but requiring user interaction, and limited impact to integrity only. No public exploits have been reported yet, and no patches are currently linked, indicating that mitigation may rely on plugin updates or manual nonce implementation. This vulnerability is particularly relevant for organizations relying on WordPress-based email subscription management, as subscriber data loss can disrupt marketing efforts and customer engagement.

Potential Impact

For European organizations, the primary impact of this vulnerability is the potential unauthorized deletion of email subscribers, which can lead to loss of valuable customer or user contact information and disrupt marketing or communication campaigns. While the vulnerability does not compromise sensitive subscriber data confidentiality or system availability, it undermines data integrity and trust in the subscription management process. Organizations with large subscriber bases or those that rely heavily on email marketing may experience operational setbacks and reputational damage if subscriber lists are manipulated. Additionally, repeated exploitation could cause administrative overhead to restore lost data and investigate incidents. Since exploitation requires tricking an administrator into clicking a malicious link, organizations with less security awareness or insufficient user training are at higher risk. The lack of known exploits in the wild reduces immediate threat but does not eliminate the risk of future attacks, especially as the vulnerability is publicly disclosed. European entities using this plugin should consider the impact on GDPR compliance, as subscriber data integrity is critical for lawful data processing and communication consent management.

Mitigation Recommendations

To mitigate CVE-2025-10691, European organizations should: 1) Monitor for and apply any official patches or updates released by yudiz promptly once available. 2) If no patch is available, implement manual nonce validation in the show_editsub_page() function to ensure all state-changing requests require a valid security token. 3) Educate and train WordPress administrators on the risks of CSRF and the importance of not clicking suspicious or unsolicited links, especially when logged into administrative accounts. 4) Employ web application firewalls (WAFs) with CSRF protection rules to detect and block forged requests targeting the plugin’s endpoints. 5) Limit administrative access to trusted networks or use multi-factor authentication to reduce the risk of compromised admin sessions. 6) Regularly back up subscriber data to enable recovery in case of unauthorized deletions. 7) Conduct security audits of WordPress plugins to identify and remediate similar vulnerabilities proactively. These measures combined will reduce the risk of exploitation and limit potential damage.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-09-18T14:54:06.118Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690c1959fd0d6d226485656f

Added to database: 11/6/2025, 3:43:21 AM

Last enriched: 11/6/2025, 3:58:08 AM

Last updated: 11/6/2025, 5:24:56 AM

Views: 5

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats