Read the docs
TI-2026-75234 Aliases CVE-2026-92553GHSA-2875-475c-qvhr

Arbitrary file upload in YaySMTP WordPress plugin enables code execution

Priority MEDIUM 41CWE-434Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-434.

Summary

The YaySMTP WP Mail SMTP plugin for WordPress is vulnerable to arbitrary file upload in all versions up to and including 2.7.7 through its putFile function. The function does not validate file types enough, since sanitize_file_name() leaves executable extensions in place and no allow-list or MIME check is applied. An authenticated attacker with subscriber-level access or above can upload files that may be executable, which can lead to remote code execution. The only guard is a .htaccess file that nginx and Apache with AllowOverride None ignore, so remote code execution is fully achievable on those configurations.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00559 46th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
YayCommerceYaySMTP – WP Mail SMTP with Email Logs, Tracking & Reportsup to 2.7.7—No fix listedCNA
  • YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports VendorYayCommerce Affected up to 2.7.7 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for YaySMTP WP Mail SMTP with Email Logs, Tracking & Reports.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Timeline

  1. 2026-10-16 Threatist record created from CVE-2026-92553
  2. 2026-10-16 Priority changed: LOW → MEDIUM
  3. 2026-10-16 Alias added: GHSA-2875-475c-qvhr

References

Other 8

  • TI-2024-06722 Unrestricted file upload in YayCommerce YayExtra – WooCommerce Extra Product Options CVSS 3.1CRITICAL 9.8
  • TI-2025-41603 WordPress YayCurrency plugin <= 3.3 - Arbitrary Content Deletion vulnerability CVSS 3.1HIGH 7.5
  • TI-2025-37443 WordPress YayPricing plugin <= 3.5.3 - Broken Access Control vulnerability CVSS 3.1HIGH 7.5
  • TI-2025-03017 SMTP for Amazon SES – YaySMTP <= 1.8 - Unauthenticated Stored Cross-Site Scripting via Email Logs CVSS 3.1HIGH 7.2
  • TI-2025-00812 Vulnerability: SMTP for Amazon SES <= 1.8 - Unauthenticated Stored Cross-Site Scripting via Email Logs CVSS 3.1HIGH 7.2
  • TI-2025-00808 SMTP for Sendinblue – YaySMTP <= 1.2 - Unauthenticated Stored Cross-Site Scripting via Email Logs CVSS 3.1HIGH 7.2
See all 31 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences