The EmergencyWP – Dead Man's switch & legacy deliverance plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.2. This is due to missing or incorrect nonce validation on the form_settings_ui (settings save handler, procedural include scope) function. This makes it possible for unauthenticated attackers to modify plugin settings including the minimum access role (altering WordPress role capabilities via add_cap/remove_cap), the data-erasure-on-uninstall flag, life-check timing values, the mandator email address, the confirmation page ID, and date/time formats via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVE-2026-9732 affects the EmergencyWP WordPress plugin up to version 1.4.2, according to the CVE description. A malicious site or link could trick an administrator into changing plugin settings. Business impact is limited but real: settings can affect access roles, uninstall data erasure, timing, and notification behavior.
Executive priority
Treat as a moderate-priority WordPress plugin issue. It is not reported as actively exploited, but administrator tricking could change sensitive recovery and access settings. Prioritize sites where EmergencyWP is installed on public-facing or business-critical WordPress instances.
Technical view
The issue is CWE-352 cross-site request forgery in the plugin settings save handler, identified as form_settings_ui. Sources attribute it to missing or incorrect nonce validation. Exploitation requires administrator interaction and can modify plugin configuration, including minimum access role and role capabilities via add_cap/remove_cap. CVSS is 4.3, medium.
Likely exposure
Exposure is limited to WordPress sites running EmergencyWP at versions up to and including 1.4.2, if the source description is accurate. The bundled affected-version metadata is inconsistent, so confirm installed plugin version directly.
Exploitation context
No CISA KEV listing is provided, and the source bundle does not state active exploitation. Attackers would need to persuade a logged-in site administrator to take an action such as clicking a link.
Researcher notes
The public sources identify nonce validation weakness in settings_main.php and settings update handling. The CVE description says all versions through 1.4.2 are vulnerable, but the bundled affected metadata is unclear. No fixed version is named in the provided sources.
Mitigation direction
Check the WordPress plugin page or vendor guidance for a fixed version or advisory.
Update EmergencyWP if a vendor-supported patched release is available.
Disable or remove EmergencyWP if it is not business-critical.
Limit administrator browsing and email exposure while logged into WordPress.
Review plugin settings for unauthorized changes after any suspected admin interaction.
Validation and detection
Inventory WordPress sites for the EmergencyWP plugin.
Record installed EmergencyWP versions and compare against 1.4.2 or below.
Review plugin settings for minimum access role and role-capability changes.
Check whether settings forms include valid WordPress nonce verification in the installed code.
Monitor administrative activity for unexpected plugin setting changes.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.