# CVE-2022-2370: YaySMTP < 2.2.1 - Subscriber+ SMTP Credentials Leak

> Authenticated subscribers can retrieve SMTP credentials due to missing capability checks in the YaySMTP WordPress plugin settings.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 1 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7vqg-r6cw-6w76

## What is CVE-2022-2370?

CVE-2022-2370 is a medium-severity missing authorization vulnerability in Unknown YaySMTP, published on 1 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The YaySMTP WordPress plugin before 2.2.1 does not have capability check before displaying the Mailer Credentials in JS code for the settings, allowing any authenticated users, such as subscriber to retrieve them

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-2370?

It affects 1 product.


Products: Yaycommerce Yaysmtp.

## How do I fix CVE-2022-2370?

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

## Is CVE-2022-2370 being exploited?

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

## Other vulnerabilities in Unknown YaySMTP

- [CVE-2025-0918](https://insights.sbomify.com/CVE-2025-0918/): SMTP for SendGrid – YaySMTP <= 1.4 - Unauthenticated Stored Cross-Site Scripting via Email Logs (high 7.2)
- [CVE-2025-0953](https://insights.sbomify.com/CVE-2025-0953/): SMTP for Sendinblue – YaySMTP <= 1.2 - Unauthenticated Stored Cross-Site Scripting via Email Logs (high 7.2)
- [CVE-2025-0916](https://insights.sbomify.com/CVE-2025-0916/): YaySMTP 2.4.9 - 2.6.2 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2023-3093](https://insights.sbomify.com/CVE-2023-3093/): YaySMTP <= 2.4.5 - Unauthenticated Stored Cross-Site Scripting via Email (high 7.2)
- [CVE-2022-2371](https://insights.sbomify.com/CVE-2022-2371/): YaySMTP < 2.2.1 - Subscriber+ Stored Cross-Site Scripting (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2370 and fix it if it is affected.

What it is: CVE-2022-2370 is a medium-severity missing authorization vulnerability in Unknown YaySMTP, published on 1 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2370 in the wild and no public exploit code.

Affected product: Unknown YaySMTP. 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-2022-2370/ (Markdown: https://insights.sbomify.com/CVE-2022-2370/index.md)
```

## Sources

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

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