← Back to the live CVE advisory feed

CVE-2026-92553: YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports

Severity

8.8 (HIGH)

Vendor

ADOBE

Affected versions

0 through 2.7.7

Patch status

Unknown

Published

2026-10-16T07:17:14.150

Modified

2026-10-16T07:17:14.150

Why it matters

This matters because the affected product may be exposed on public websites. A vulnerable plugin can create a direct path to site compromise, malicious code deployment, or data theft.

Recommended admin actions

• Review and patch based on exposure, asset criticality, and business impact.
• Check whether the affected WordPress plugin or theme is installed.
• Update, disable, or remove the affected component if present.
• Treat internet-facing systems as higher priority.
• Review logs for suspicious activity related to the affected application or component.

Technical summary

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.

View the official NVD record for CVE-2026-92553

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.