MEDIUM 4.3

CVE-2024-35648: CSRF Vulnerability in Andy Moyle Emergency Password Reset 8.0

A cross-site request forgery (CSRF) vulnerability exists in Andy Moyle Emergency Password Reset versions up to and including 8.0. An attacker can craft a malicious web page or email that, when visited by an authenticated user, triggers unintended password reset actions without the user's knowledge or consent. The attack succeeds because the application does not properly validate the origin or intent of password reset requests.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weaknesses (CWE)
CWE-352
Affected products
0 configuration(s)
Published / Modified
2026-06-17 / 2026-06-17

NVD description (verbatim)

Cross-Site request forgery (CSRF) vulnerability in Andy Moyle Emergency Password Reset allows Cross Site Request Forgery. This issue affects Emergency Password Reset: from n/a through 8.0.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2024-35648 is a CSRF vulnerability (CWE-352) affecting the Emergency Password Reset plugin. The vulnerability stems from insufficient anti-CSRF protections in the password reset functionality. An attacker can forge requests that execute within the security context of an authenticated administrator or user session, allowing unauthorized password resets. The CVSS 3.1 score of 4.3 reflects a network-accessible, low-complexity attack requiring user interaction, with limited integrity impact and no confidentiality or availability damage in the base scenario.

Business impact

A successful CSRF attack could allow an attacker to reset passwords for user accounts without authorization, leading to account lockouts, unauthorized access if combined with credential stuffing, or disruption of emergency password recovery workflows. In organizations relying on this plugin for credential management, such attacks could compromise administrative access or frustrate legitimate users attempting to regain access to locked accounts.

Affected systems

Andy Moyle Emergency Password Reset plugin versions from initial release through version 8.0 are affected. The vendor product list is not populated in available data; organizations should verify their installed version against the plugin repository or documentation. Any WordPress site or compatible platform running this plugin at version 8.0 or earlier is potentially vulnerable.

Exploitability

This vulnerability requires user interaction—specifically, a user must visit an attacker-controlled page or click a malicious link while authenticated to the target system. No authentication is required from the attacker's perspective, and the attack vector is network-based with low complexity. However, the requirement for the victim to be logged into the vulnerable application and then interact with the attacker's payload limits the overall exploitability. This is not an unauthenticated remote code execution risk; it is a session-hijacking class of attack.

Remediation

Update the Emergency Password Reset plugin to a version newer than 8.0. Organizations should verify patch availability from the plugin author or official repository. If no patch is immediately available, consider temporarily disabling the plugin or restricting access to password reset functionality to trusted networks. Implement general CSRF defenses at the application level, such as SameSite cookie attributes and Content Security Policy headers.

Patch guidance

Check the Andy Moyle Emergency Password Reset plugin repository or the author's official advisory for versions released after June 2026. Apply available patches as soon as they are validated in a test environment. If the plugin is embedded in a larger application or custom stack, coordinate with your development team to ensure compatibility. Verify the patch resolves the CSRF token validation and request origin checks.

Detection guidance

Monitor for POST requests to password reset endpoints that originate from unexpected referrers or lack proper CSRF tokens. Log and alert on password reset actions triggered by users who did not initiate the request through the normal UI. Review web server access logs and WAF logs for patterns consistent with CSRF exploitation, such as requests with missing or invalid Referer headers. Implement application-level logging to track all password reset events, including timestamp, user, and request source.

Why prioritize this

Although this vulnerability carries a MEDIUM severity score, it directly threatens account security and administrative access. In environments where the Emergency Password Reset plugin is used to manage critical access workflows, CSRF attacks could enable account takeover or lockout scenarios. The plugin's name suggests it is deployed for emergency purposes, making it a high-value target. Prioritize patching in production environments, particularly where admin accounts are managed through this plugin. This vulnerability is not yet in the CISA KEV catalog, but organizations should not delay remediation based on KEV status alone.

Risk score, explained

The CVSS 3.1 score of 4.3 (MEDIUM) reflects the attack vector (network, no special access required), complexity (low), and impact (limited to integrity—unauthorized password resets). The requirement for user interaction (UI:R) prevents a higher score. However, the contextual risk depends on deployment scope: if this plugin manages access to high-value systems or admin accounts, the true risk may exceed the base score. Organizations should factor in their threat landscape and the criticality of accounts managed by this plugin.

Frequently asked questions

What exactly can an attacker do with a CSRF vulnerability in a password reset function?

An attacker can trigger a password reset for a targeted user account by tricking that user into visiting a malicious page while logged into the vulnerable application. This does not grant the attacker the new password, but it can lock the legitimate user out of their account or, in some configurations, trigger a password reset email to an attacker-controlled address. The attacker's goal is typically to disrupt access or create a window of opportunity for further compromise.

Do I need to be logged in to the application to be vulnerable to this attack?

Yes. The victim must be authenticated to the target system for the CSRF payload to succeed. The attacker is betting that your users access the vulnerable plugin from within an authenticated browser session, then click on a malicious link or visit an attacker-controlled site without logging out. This is a realistic scenario in many organizations.

Is there a CISA KEV entry for this vulnerability?

No, as of the data provided, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. However, KEV status is not an indicator of exploit availability or real-world risk; it simply means CISA has not yet confirmed active exploitation in the wild. Do not defer patching pending KEV inclusion.

What if the plugin author has not released a patch yet?

Temporary mitigations include disabling the plugin if it is not mission-critical, restricting access to the password reset endpoint to specific IP ranges, implementing strict CSRF tokens at the web server level via WAF rules, and enabling SameSite cookie policies. Monitor the plugin repository and the vendor's security advisories regularly for patch availability.

This analysis is based on CVE-2024-35648 as published and may be updated as additional information becomes available. Organizations should verify their specific plugin versions and consult official vendor advisories for definitive patch information. The technical details provided are for informational and defensive purposes only. No exploit code or weaponized attack methods are provided. Risk scoring should be adapted to your organization's specific threat model and asset criticality. Source: NVD (public-domain), retrieved 2026-07-26. Analysis generated by SEC.co (claude-haiku-4-5).