SMTP2GO for WordPress <= 1.16.0 - Missing Authorization to Authenticated (Subscriber+) Log Read/Truncate
Strategic Overview
- Status
- Patched in 1.17.0
- Affected Plugin
- SMTP2GO for WordPress – Email Made Easy
- Affected Version
<= 1.16.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-7621
At a glance
CVE-2026-7621 is a medium-severity Missing Authorization vulnerability in the SMTP2GO for WordPress WordPress plugin, affecting versions <= 1.16.0. 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 1.17.0; sites on affected versions should update now. Disclosed May 2026, reported by normaandersonfrank.
Vulnerability Overview
The SMTP2GO for WordPress – Email Made Easy plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.16.0. 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 truncate all SMTP2GO log records from the database or download a CSV export of all SMTP log data including recipient addresses, sender addresses, message subjects, and API response data.
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
Reaching this weakness in SMTP2GO for WordPress <= 1.16.0 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 SMTP2GO for WordPress the fix is 1.17.0: builds <= 1.16.0 are affected, anything from 1.17.0 onward is not.
Remediation
Update to version 1.17.0, 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: SMTP2GO for WordPress 1.17.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in SMTP2GO for WordPress – Email Made Easy
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C