CVE-2026-92553

waiting for further signalsZero needs more public information before it can validate it.

GHSA-2875-475c-qvhr ↗EUVD-2026-102789 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports <= 2.7.7
ETK-2026-1765Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 16h 40msince last run
32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+29h26m
0
+2h
+4h
+6h
+8h
+10h

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.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.58%46th percentile
agent run time
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 06:41Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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.

  1. 2026-10-16 06:41Z
    ghsa: trigger signal, started the run
  2. 2026-10-16 06:41Z

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 04:45Z

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.