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-14853: CWE-352 Cross-Site Request Forgery (CSRF) in smings LEAV Last Email Address Validator

0
Medium
VulnerabilityCVE-2025-14853cvecve-2025-14853cwe-352
Published: Fri Jan 16 2026 (01/16/2026, 06:43:21 UTC)
Source: CVE Database V5
Vendor/Project: smings
Product: LEAV Last Email Address Validator

Description

The LEAV Last Email Address Validator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions <= 1.7.1. This is due to missing or incorrect nonce validation on the display_settings_page function. This makes it possible for unauthenticated attackers to modify 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

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:38:57 UTC

Technical Analysis

The LEAV Last Email Address Validator plugin for WordPress, developed by smings, suffers from a Cross-Site Request Forgery (CSRF) vulnerability identified as CVE-2025-14853. This vulnerability exists in all versions up to and including 1.7.1 due to missing or incorrect nonce validation in the display_settings_page function. Nonces in WordPress are security tokens used to verify that requests originate from legitimate users and prevent unauthorized actions. The absence or improper implementation of nonce checks allows attackers to craft malicious requests that, when executed by an authenticated administrator (via clicking a link or visiting a crafted webpage), can modify plugin settings without the administrator's explicit consent. Since the vulnerability does not require authentication but does require user interaction, it is exploitable remotely with low complexity. The impact is limited to integrity, as attackers can change plugin configurations, potentially leading to misbehavior or further exploitation vectors. Confidentiality and availability are not directly affected. The CVSS v3.1 base score is 4.3, reflecting a medium severity rating. No public exploits have been reported yet, but the vulnerability's presence in a popular WordPress plugin makes it a relevant risk for websites relying on this plugin for email validation.

Potential Impact

The primary impact of this vulnerability is the unauthorized modification of plugin settings, which compromises the integrity of the affected WordPress site’s configuration. Attackers could alter validation parameters or disable security features, potentially enabling further attacks such as spam, phishing, or injection of malicious data. While confidentiality and availability are not directly impacted, the integrity breach can serve as a stepping stone for more severe attacks if combined with other vulnerabilities or misconfigurations. Organizations running WordPress sites with this plugin are at risk of silent configuration changes that may degrade security posture or user trust. Given WordPress’s widespread use globally, especially among small to medium businesses and content-driven sites, the scope is significant. The requirement for administrator interaction limits automated mass exploitation but targeted phishing or social engineering campaigns could be effective. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat of future exploitation.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately update the LEAV Last Email Address Validator plugin to a version that includes proper nonce validation once it is released by the vendor. Until a patch is available, administrators should implement the following specific measures: (1) Restrict administrative access to trusted networks and users to reduce exposure to phishing attempts; (2) Educate administrators about the risks of clicking on unsolicited or suspicious links, especially those that could trigger plugin settings changes; (3) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests targeting the plugin’s settings endpoints; (4) Regularly audit plugin configurations and logs for unauthorized changes; (5) Consider temporarily disabling or removing the plugin if it is not critical to operations; (6) Use multi-factor authentication (MFA) for WordPress admin accounts to reduce the risk of compromised credentials facilitating further attacks. These targeted steps go beyond generic advice by focusing on reducing the attack surface and detecting exploitation attempts specific to this CSRF vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-17T20:29:58.227Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6969e18d7c726673b606412d

Added to database: 1/16/2026, 6:58:21 AM

Last enriched: 2/27/2026, 11:38:57 AM

Last updated: 3/24/2026, 7:53:35 AM

Views: 65

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses