CVE-2026-92553

8.8High

Published 16 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

8.8High

Attack vector: Network
Complexity: Low
Privileges needed: Low
User interaction: None
Impact: Full C/I/A compromise
Weakness: CWE-434

Impact

Authenticated users with subscriber access or higher can achieve remote code execution by uploading executable files. This works directly on nginx or Apache setups with AllowOverride None, where the plugin's .htaccess protection is ignored.

Root cause

The putFile function relies on sanitize_file_name() without checking MIME types, enforcing an extension allow-list, or renaming executable extensions.

Affected systems

YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports plugin for WordPress versions up to and including 2.7.7

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Fix & remediation

Upgrade YaySMTP to a version newer than 2.7.7 once available. If you cannot patch immediately, deactivate the plugin or block direct execution/access to the plugin upload directory in your web server configuration.

shell

$ wp plugin update yaysmtp

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

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

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-92553