CVE-2026-92553
waiting for further signalsZero needs more public information before it can validate it.GHSA-2875-475c-qvhr ↗EUVD-2026-102789 ↗
description
YaySMTP for WordPress versions through 2.7.7 permit insufficiently restricted file uploads. An authenticated user with Subscriber-level access or greater may upload executable content, potentially leading to server-side code execution on configurations that do not enforce the plugin's access-control file.
mitigation
Disable YaySMTP until a patched release is available, as no fixed version is recorded. Restrict WordPress accounts to trusted users and configure the web server to deny access to and execution of uploaded plugin files; do not rely solely on .htaccess protections under nginx or Apache with overrides disabled.
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-16 06:41Zghsa: trigger signal, started the run
- 2026-10-16 06:41Zcve.org record for CVE-2026-92553
this entry in the feed
GET /api/v1/feed/CVE-2026-92553
{ "etk_id": "ETK-2026-1765", "cve_id": "CVE-2026-92553", "display_id": "CVE-2026-92553", "ghsa_id": "GHSA-2875-475c-qvhr", "euvd_id": "EUVD-2026-102789", "status": "published", "anchor_state": "anchored", "title": "Arbitrary file upload in YaySMTP WordPress plugin", "summary": "YaySMTP for WordPress versions through 2.7.7 permit insufficiently restricted file uploads. An authenticated user with Subscriber-level access or greater may upload executable content, potentially leading to server-side code execution on configurations that do not enforce the plugin's access-control file.", "mitigation": "Disable YaySMTP until a patched release is available, as no fixed version is recorded. Restrict WordPress accounts to trusted users and configure the web server to deny access to and execution of uploaded plugin files; do not rely solely on .htaccess protections under nginx or Apache with overrides disabled.", "vendor": "yaycommerce", "product": "YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 2.7.7" ], "ecosystem": null, "fixed_versions": [], "package_name": "YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports", "purl": null } ], "cwes": null, "cvss_score": 8.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "epss_score": 0.0058, "epss_percentile": 0.4643, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 32.0919192, "t0_at": "2026-10-16T06:41:03.415000+00:00", "signals": { "trigger_signal": { "at": "2026-10-16T06:41:03.415000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-16T06:41:03.415000+00:00", "url": "https://github.com/advisories/GHSA-2875-475c-qvhr" } } }
published 2026-10-16 10:48Z
last change 2026-10-21 17:00Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.