CVE-2026-92553: CWE-434 Unrestricted Upload of File with Dangerous Type in yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports
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.
CVSS v3.1
Score 8.8high
Affected software
yaycommerce
YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-92553 is a high-severity vulnerability in the YaySMTP WordPress plugin (versions up to 2.7.7) caused by improper validation of uploaded files in the putFile function. The sanitize_file_name() function does not remove executable extensions, and no allow-list, MIME type checks, or safe-extension renaming is performed. Authenticated attackers with subscriber-level privileges can upload files that may be executed remotely, especially on servers where the .htaccess-based protection is ignored, such as nginx or Apache with AllowOverride None, leading to remote code execution.
Potential Impact
An attacker with subscriber-level access or higher can upload arbitrary files that may be executed on the server, resulting in remote code execution. This can lead to full compromise of the affected WordPress site and potentially the underlying server, impacting confidentiality, integrity, and availability.
Mitigation Recommendations
No official patch or fix is currently documented. Users should monitor the vendor advisory for updates. Until a fix is available, restrict subscriber-level access and consider disabling or removing the vulnerable plugin. Server administrators using nginx or Apache with AllowOverride None should be aware that the .htaccess protection is ineffective. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-09-16T13:11:57.702Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad1cc6e2cdf04f656c71866
Added to database: 10/16/2026, 07:04:14 UTC
Last enriched: 10/16/2026, 07:18:20 UTC
Last updated: 10/16/2026, 19:03:29 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.