---
id: "CVE-2026-92553"
kind: "vulnerability"
aliases: ["CVE-2026-92553"]
title: "WordPress YaySMTP plugin: subscriber uploads can run code on server"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["nginx", "package", "self-hosted", "wordpress", "wp-plugins"]
not_affected_if: ["no-subscriber-accounts-or-registration", "plugin-not-installed", "version-above-2.7.7"]
published_at: "2026-10-16T07:17:14+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-23T22:34:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-92553", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# WordPress YaySMTP plugin: subscriber uploads can run code on server

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

Check the installed YaySMTP plugin version in the WordPress admin plugins list; anything at or below 2.7.7 is affected.
On the server, check whether the web server ignores .htaccess (nginx, or Apache with AllowOverride None) in the plugin's upload directory.

## Fix

Update YaySMTP to a version later than 2.7.7; the sources do not name the fixed version.

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-92553

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_