Authenticated code execution via unchecked attachment extensions
Published Oct 16, 2026 · Updated Oct 16, 2026
File upload in YayCommerce YaySMTP 2.7.7 and earlier allows remote authenticated users to execute code via email attachments. The putFile function uses sanitize_file_name() but preserves executable extensions without an extension allowlist, MIME validation, or safe-extension rename. Subscriber-level access suffices; code execution requires executable uploads and ineffective writeGuards() .htaccess protection, as on nginx or Apache with AllowOverride None.
Summary
What happened
File upload in YayCommerce YaySMTP 2.7.7 and earlier allows remote authenticated users to execute code via email attachments. The putFile function uses sanitize_file_name() but preserves executable extensions without an extension allowlist, MIME validation, or safe-extension rename. Subscriber-level access suffices; code execution requires executable uploads and ineffective writeGuards() .htaccess protection, as on nginx or Apache with AllowOverride None.
The record
- CVE
- CVE-2026-92553
- Published
- Oct 16, 2026
- Updated
- Oct 16, 2026
- Vendor
- YayCommerce
- Product
- YaySMTP
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 16, 2026CVE publishedPublication date reported by the CVE source.
- Oct 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.7.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started