# CVE-2019-25141: Easy WP SMTP <= 1.3.9 - Missing Authorization to Arbitrary Options Update

> Unauthenticated attackers can modify plugin settings and inject new admin accounts due to missing capability checks in the Easy WP SMTP plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rpx2-wvxr-qvrr

## What is CVE-2019-25141?

CVE-2019-25141 is a critical missing authorization vulnerability in smub Easy WP SMTP – WordPress SMTP and Email Logs: Gmail, Office 365, Outlook, Custom SMTP, and more, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Easy WP SMTP plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 1.3.9. This is due to missing capability checks on the admin_init() function, in addition to insufficient input validation. This makes it possible for unauthenticated attackers to modify the plugins settings and arbitrary options on the site that can be used to inject new administrative user accounts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-25141?

It affects 1 product.


Products: Wp-Ecommerce Easy Wp Smtp.

## How do I fix CVE-2019-25141?

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

## Is CVE-2019-25141 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25141 exists.

Public exploit code:

- Easy WP SMTP <= 1.3.9 - Missing Authorization to Arbitrary Options Update (nuclei): http/cves/2019/CVE-2019-25141.yaml

## Other vulnerabilities in smub Easy WP SMTP – WordPress SMTP and Email Logs: Gmail, Office 365, Outlook, Custom SMTP, and more

- [CVE-2022-42699](https://insights.sbomify.com/CVE-2022-42699/): WordPress Easy WP SMTP Plugin <= 1.5.1 is vulnerable to Remote Code Execution (RCE) (critical 9.1)
- [CVE-2022-45829](https://insights.sbomify.com/CVE-2022-45829/): WordPress Easy WP SMTP Plugin <= 1.5.1 is vulnerable to Arbitrary File Deletion (high 8.7)
- [CVE-2020-35234](https://insights.sbomify.com/CVE-2020-35234/): Information disclosure in n/a (high 7.5)
- [CVE-2022-3334](https://insights.sbomify.com/CVE-2022-3334/): Easy WP SMTP < 1.5.0 - Admin+ PHP Objection Injection (high 7.2)
- [CVE-2022-45833](https://insights.sbomify.com/CVE-2022-45833/): WordPress Easy WP SMTP Plugin <= 1.5.1 is vulnerable to Directory Traversal (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25141 and fix it if it is affected.

What it is: CVE-2019-25141 is a critical missing authorization vulnerability in smub Easy WP SMTP – WordPress SMTP and Email Logs: Gmail, Office 365, Outlook, Custom SMTP, and more, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25141 exists.

Affected product: smub Easy WP SMTP – WordPress SMTP and Email Logs: Gmail, Office 365, Outlook, Custom SMTP, and more. 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-2019-25141/ (Markdown: https://insights.sbomify.com/CVE-2019-25141/index.md)
```

## Sources

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

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