CVE-2026-92553YaySMTP <= 2.7.7 - Authenticated (Subscriber+) Arbitrary File Upload via Attachment Filename Extension
- 8.8HighCVSS base score
- 0.56%Exploitation in 30 daysEPSS · top 53% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Wordfence
- 30 days later
· 30 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WordfenceCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.56% · top 53% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
yaycommerce · YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports
- affected ≤ 2.7.7
References
References8
- https://www.wordfence.com/threat-intel/vulnerabilities/id/4abbf148-4648-440c-8a82-cf68bf051fbe?source=cve (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L542 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L549 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L178 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L106 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/Utils.php#L814 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/PluginCore.php#L37 (opens in a new tab)
- https://plugins.trac.wordpress.org/changeset/3739875/yaysmtp/trunk/includes/Helper/EmailLogAttachments.php (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-102789 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-92553)Record last updated .