Live › vulnerability › CVE-2026-92553
Go to dashboardThe YaySMTP WordPress mail plugin up to version 2.7.7 lets any logged-in subscriber upload files through its putFile function without type checks. On nginx, or on Apache with AllowOverride None, the .htaccess guard is ignored, so an uploaded PHP file can be run, giving the attacker remote code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
2.7.7 is affectedUpdate YaySMTP to a version later than 2.7.7; the sources do not name the fixed version.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-92553")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.