Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesYaySMTP

YaySMTP vulnerabilities

YaySMTP has 8 known vulnerabilities in this database. The most recent published record is dated 6 Nov 2026.

Known vulnerabilities
8
Active installs
10,000+
Latest version
2.7.9
Last updated
1 Nov 2026
Most recent
6 Nov 2026

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
SQL injection
CVE-2026-109977
Medium 4.9Up to 2.7.8Fixed in a later version (latest 2.7.9)6 Nov 2026
Remote code execution
CVE-2026-92553
High 8.8Up to 2.7.7Fixed in a later version (latest 2.7.9)16 Oct 2026
Cross-site scripting (XSS)
CVE-2025-0916
High 7.2Before 2.6.3Fixed in 2.6.319 Feb 2025
Cross-site scripting (XSS)
CVE-2023-3093
High 7.2Before 2.4.6Fixed in 2.4.612 Jul 2023
Cross-site scripting (XSS)
CVE-2022-2372
Medium 4.8Before 2.2.2Fixed in 2.2.28 Aug 2022
Cross-site scripting (XSS)
CVE-2022-2371
Medium 5.4Before 2.2.1Fixed in 2.2.18 Aug 2022
Broken access control
CVE-2022-2369
Medium 4.3Before 2.2.1Fixed in 2.2.11 Aug 2022
Broken access control
CVE-2022-2370
Medium 6.5Before 2.2.1Fixed in 2.2.11 Aug 2022
Read the published descriptions
CVE-2026-109977, 6 Nov 2026
The YaySMTP - WP Mail SMTP with Email Logs, Tracking & Reports plugin for WordPress is vulnerable to time-based SQL Injection via the 'params[searchKey]' parameter in all versions up to, and including, 2.7.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
CVE-2026-92553, 16 Oct 2026
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. CVE record
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.

Get website support