Plugins · yaysmtp · data as of 2026-11-04
Is YaySMTP safe? Known vulnerabilities and latest version
- Latest version
- 2.7.9
- Last updated
- 2026-11-01
- Active installs
- 10,000+
- Known issues on record
- 9
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 5.4+
Free WordPress SMTP plugin with email logs, open & click tracking, reports & charts, CSV export, and WooCommerce email preview. — by YayCommerce
What to do
- Update to the latest version (2.7.9). Anything older than 2.7.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get yaysmtp --field=version shows what you run; wp plugin update yaysmtp updates it.
Check your version
Known vulnerabilities
9 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 8.8 CVE-2026-92553 · published 2026-10-16
Arbitrary file upload in YaySMTP (2.7.7 and older)
- Affected
- 2.7.7 and older
- Fixed in
- 2.7.8 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.7.7 via the putFile function. This is due to insufficient file type validation in the putFile function, as sanitize_file_name() does not strip executable extensions and no allow-list, MIME check, or safe-extension rename is applied. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. The only server-side guard is a .htaccess file containing 'Require all denied' written by writeGuards(), which is silently ignored by nginx and by Apache configured with AllowOverride None, meaning RCE is fully achievable on those server configurations.
NVD CVE-2026-92553Wordfence advisoryCode change (fix)Plugin source
high 7.6 CVE-2025-53256 · published 2025-06-27
SQL injection in YaySMTP (2.6.6 and older)
- Affected
- 2.6.6 and older
- Fixed in
- 2.6.7
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in YayCommerce YaySMTP yaysmtp allows SQL Injection.This issue affects YaySMTP: from n/a through <= 2.6.6.
high 7.6 CVE-2025-47587 · published 2025-05-07
SQL injection in YaySMTP (2.6.4 and older)
- Affected
- 2.6.4 and older
- Fixed in
- 2.6.5
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in YayCommerce YaySMTP yaysmtp allows Blind SQL Injection.This issue affects YaySMTP: from n/a through <= 2.6.4.
medium 6.1 CVE-2025-0916 · published 2025-02-19
Stored cross-site scripting (XSS) in YaySMTP (2.4.9 to 2.6.2)
- Affected
- 2.4.9 to 2.6.2
- Fixed in
- 2.6.3 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2025-0916Wordfence advisoryCode change (fix)wordpress.orgPlugin source
medium 6.1 CVE-2023-3093 · published 2023-07-12
Stored cross-site scripting (XSS) in YaySMTP (2.4.5 and older)
- Affected
- 2.4.5 and older
- Fixed in
- 2.4.6 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
medium 4.8 CVE-2022-2372 · published 2022-08-08
Stored cross-site scripting (XSS) in YaySMTP (older than 2.2.2)
- Affected
- older than 2.2.2
- Fixed in
- 2.2.2
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
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)
medium 5.4 CVE-2022-2371 · published 2022-08-08
Stored cross-site scripting (XSS) in YaySMTP (older than 2.2.1)
- Affected
- older than 2.2.1
- Fixed in
- 2.2.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
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.
medium 4.3 CVE-2022-2369 · published 2022-08-01
Missing authorization check in YaySMTP (older than 2.2.1)
- Affected
- older than 2.2.1
- Fixed in
- 2.2.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- NVD analysis · score by NVD
Details from the advisory
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
medium 6.5 CVE-2022-2370 · published 2022-08-01
Missing authorization check in YaySMTP (older than 2.2.1)
- Affected
- older than 2.2.1
- Fixed in
- 2.2.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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
Recent activity
- 2026-11-01 — latest release on wordpress.org (2.7.9).
- 2026-10-16 — Arbitrary file upload disclosed (CVE-2026-92553), fixed in 2.7.8.
- 2025-06-27 — SQL injection disclosed (CVE-2025-53256), fixed in 2.6.7.
- 2025-05-07 — SQL injection disclosed (CVE-2025-47587), fixed in 2.6.5.
Get an email when YaySMTP has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for YaySMTP (yaysmtp) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by YayCommerce (4 tracked)
Types found in this plugin: Cross-site scripting (XSS) (4) · SQL injection (2) · Missing authorization (2) · Arbitrary file upload (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/yaysmtp (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/yaysmtp"><img src="https://laskyr.com/plugins/yaysmtp/badge.svg" alt="YaySMTP vulnerability status"></a>