HomeWordPress vulnerabilitiesYaySMTP
YaySMTP vulnerabilities
YaySMTP has 6 known vulnerabilities in this database. The most recent published record is dated 19 Feb 2025.
- Known vulnerabilities
- 6
- Active installs
- 10,000+
- Latest version
- 2.7.7
- Last updated
- 14 Sep 2026
- Most recent
- 19 Feb 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2025-0916 | High 7.2 | Before 2.6.3 | Fixed in 2.6.3 | 19 Feb 2025 |
| Cross-site scripting (XSS) CVE-2023-3093 | High 7.2 | Before 2.4.6 | Fixed in 2.4.6 | 12 Jul 2023 |
| Cross-site scripting (XSS) CVE-2022-2372 | Medium 4.8 | Before 2.2.2 | Fixed in 2.2.2 | 8 Aug 2022 |
| Cross-site scripting (XSS) CVE-2022-2371 | Medium 5.4 | Before 2.2.1 | Fixed in 2.2.1 | 8 Aug 2022 |
| Broken access control CVE-2022-2369 | Medium 4.3 | Before 2.2.1 | Fixed in 2.2.1 | 1 Aug 2022 |
| Broken access control CVE-2022-2370 | Medium 6.5 | Before 2.2.1 | Fixed in 2.2.1 | 1 Aug 2022 |
Read the published descriptions
- CVE-2025-0916, 19 Feb 2025
- The YaySMTP and Email Logs: Amazon SES, SendGrid, Outlook, Mailgun, Brevo, Google and Any SMTP Service plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions 2.4.9 to 2.6.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Note: The vulnerability has been initially patched in version 2.4.8 and was reintroduced in version 2.4.9 with the removal of the wp_kses_post() built-in WordPress sanitization function. CVE record
- CVE-2023-3093, 12 Jul 2023
- The YaySMTP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via email contents in versions up to, and including, 2.4.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2022-2372, 8 Aug 2022
- The YaySMTP WordPress plugin before 2.2.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2022-2371, 8 Aug 2022
- 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. CVE record
- CVE-2022-2369, 1 Aug 2022
- The YaySMTP WordPress plugin before 2.2.1 does not have capability check in an AJAX action, allowing any logged in users, such as subscriber to view the Logs of the plugin CVE record
- CVE-2022-2370, 1 Aug 2022
- 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 CVE record
What to do if you run YaySMTP
If you run YaySMTP, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new YaySMTP vulnerabilities
Free. We email you when a new vulnerability is published for YaySMTP, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.