CVE-2026-92553 YaySMTP <= 2.7.7 - Authenticated (Subscriber+) Arbitrary File Upload via Attachment Filename Extension
Authenticated subscribers can upload executable files via attachment filenames, leading to remote code execution on servers ignoring .htaccess guards.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-92553?
CVE-2026-92553 is a high-severity vulnerability in yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-434
Which versions are affected by CVE-2026-92553?
How do I fix CVE-2026-92553?
No fix has been published for CVE-2026-92553 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-92553 being exploited?
There is no known exploitation of CVE-2026-92553 in the wild and no public exploit code.
Sources
Also known as GHSA-2875-475c-qvhr.