CVE Catalog

CVE-2026-92553

HighCVSS 8.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.58%

46th percentile - higher than 46% of all known CVEs

Summary

The YaySMTP plugin for WordPress (versions up to and including 2.7.7) is vulnerable to arbitrary file upload via the putFile function. Insufficient file type validation allows an authenticated subscriber-level user to upload an executable file, leading to remote code execution (RCE). The .htaccess protection is ignored by nginx and Apache with AllowOverride None.

Risk Assessment

A low-privileged attacker can take over the server by executing arbitrary code. The risk is especially high on nginx or Apache servers without AllowOverride.

Recommendation

Update the YaySMTP plugin to a version newer than 2.7.7. Review server configuration and consider disabling file execution in the uploads directory.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS