# CVE-2026-7621: SMTP2GO for WordPress <= 1.16.0 - Missing Authorization to Authenticated (Subscriber+) Log Read/Truncate

> Authenticated subscribers can read or delete SMTP2GO email logs due to missing authorization checks in the WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-j6m5-8x48-22mr

## What is CVE-2026-7621?

CVE-2026-7621 is a medium-severity missing authorization vulnerability in SMTP2GO for WordPress – Email Made Easy, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-7621?


## How do I fix CVE-2026-7621?

No fix has been published for CVE-2026-7621 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7621 being exploited?

There is no known exploitation of CVE-2026-7621 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7621 and fix it if it is affected.

What it is: CVE-2026-7621 is a medium-severity missing authorization vulnerability in SMTP2GO for WordPress – Email Made Easy, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7621 in the wild and no public exploit code.

Affected product: SMTP2GO for WordPress – Email Made Easy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7621/ (Markdown: https://insights.sbomify.com/CVE-2026-7621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7621
- OSV: https://osv.dev/vulnerability/CVE-2026-7621

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7621/
Summaries are generated and may contain mistakes; the official description above is the record.