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.
Published: 2026-10-16
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution
Action: Patch Immediately
AI Analysis

Impact

The plugin suffers from an arbitrary file upload flaw caused by missing or incomplete file type validation. The putFile function in the code accepts any file name with an executable extension because sanitize_file_name() does not strip such extensions and there is no allow‑list, MIME check or safe‑extension rename. As a result, an authenticated user with subscriber‑level or higher privileges can upload executable files, allowing an attacker to place malicious code on the server and trigger remote code execution.

Affected Systems

Yaycommerce’s YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports plugin for WordPress is affected, with all versions up to and including 2.7.7. No later versions are known to be impacted and no other products from the vendor are listed.

Risk and Exploitability

The CVSS score of 8.8 classifies the vulnerability as High, and the EPSS score of 0.00575 (<1%) indicates a very low probability of exploitation by the general population. The plugin’s sole server‑side guard is a .htaccess file containing 'Require all denied', but this rule is silently ignored by nginx and by Apache configured with AllowOverride None, making the risk of remote code execution fully realizable on those server configurations. Because the flaw requires authentication, the attacker must be able to log in as a subscriber or higher, but once access is achieved, uploading the file is sufficient to execute code.

Generated by OpenCVE AI on October 16, 2026 at 15:54 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the YaySMTP plugin to the latest version, which removes the vulnerable putFile logic.
  • Reconfigure the web server to deactivate execution of uploaded files in the plugin’s attachment directory, for example by adding a .htaccess rule or server block that denies script execution.
  • Limit file upload capabilities for subscriber‑level users, or disable the upload feature entirely for accounts that do not require it.

Generated by OpenCVE AI on October 16, 2026 at 15:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 16 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
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.
Title YaySMTP <= 2.7.7 - Authenticated (Subscriber+) Arbitrary File Upload via Attachment Filename Extension
Weaknesses CWE-434
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-16T15:09:38.412Z

Reserved: 2026-09-16T13:11:57.702Z

Link: CVE-2026-92553

cve-icon Vulnrichment

Updated: 2026-10-16T14:59:46.675Z

cve-icon NVD

Status : Deferred

Published: 2026-10-16T07:17:14.150

Modified: 2026-10-16T15:17:35.653

Link: CVE-2026-92553

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T16:00:12Z

Weaknesses
  • CWE-434

    Unrestricted Upload of File with Dangerous Type