Gravity SMTP <= 2.1.4 - Missing Authorization to Authenticated (Subscriber+) Plugin Uninstall
Strategic Overview
- Status
- Patched in 2.1.5
- Affected Plugin
- Gravity SMTP
- Affected Version
<= 2.1.4- CVSS
- 7.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-4162
At a glance
CVE-2026-4162 is a high-severity Missing Authorization vulnerability in the Gravity SMTP WordPress plugin, affecting versions <= 2.1.4. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.5; sites on affected versions should update now. Disclosed April 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).
Vulnerability Overview
The Gravity SMTP plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.1.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to uninstall and deactivate the plugin and delete plugin options. NOTE: This vulnerability is also exploitable via a Cross-Site Request Forgery vector.
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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Reaching this weakness in Gravity SMTP <= 2.1.4 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 Gravity SMTP the fix is 2.1.5: builds <= 2.1.4 are affected, anything from 2.1.5 onward is not.
Remediation
Update to version 2.1.5, 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: Gravity SMTP 2.1.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Gravity SMTP
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C