CVE-2026-1930

Emailchef <= 3.5.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Settings Deletion

2026-04-21 20:35
Legion Hunter

Strategic Overview

Status
Patched in 3.5.2
Affected Plugin
Emailchef
Affected Version
<= 3.5.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1930
View all Emailchef vulnerabilities

At a glance

CVE-2026-1930 is a medium-severity Missing Authorization vulnerability in the Emailchef WordPress plugin, affecting versions <= 3.5.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.5.2; sites on affected versions should update now. Disclosed April 2026, reported by Legion Hunter.

Vulnerability Overview

The Emailchef plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the page_options_ajax_disconnect() function in all versions up to, and including, 3.5.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete the plugin's settings via the 'emailchef_disconnect' AJAX action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Emailchef <= 3.5.1 carries this weakness at emailchef_disconnect, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Emailchef the fix is 3.5.2: builds <= 3.5.1 are affected, anything from 3.5.2 onward is not.

Remediation

Update to version 3.5.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Emailchef 3.5.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C