← back to feed
CVE-2026-93550

CVE-2026-93550

validatedZero produced an exploit or a check.

GHSA-hxhg-9p9q-54v7 ↗EUVD-2026-96794 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Veeqo for WooCommerce <= 2.2.8
ETK-2026-2005Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss4.3cna vendorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
+8.9dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+8.9dagent stopped
0
+2d
+4d
+6d
+8d

description

Veeqo for WooCommerce versions 2.2.8 and earlier are affected. A Subscriber-level or higher WordPress user can cause the bridge installer to retrieve and unpack an attacker-controlled archive in the WordPress root, potentially placing PHP files there. Exploitation requires an authenticated low-privilege account.

mitigation

Deactivate and remove the plugin where it is not required, and restrict or revoke untrusted Subscriber-level accounts. No fixed release is documented; keep the plugin disabled until a vendor update is available.

check
available
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.
deterministic
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.18%6th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-11 06:00Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-11 06:00Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-93550
  2. 2026-10-20 02:55Z

this entry in the feed

GET /api/v1/feed/CVE-2026-93550

{
  "etk_id": "ETK-2026-2005",
  "cve_id": "CVE-2026-93550",
  "display_id": "CVE-2026-93550",
  "ghsa_id": "GHSA-hxhg-9p9q-54v7",
  "euvd_id": "EUVD-2026-96794",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper archive installation authorization in Veeqo for WooCommerce",
  "summary": "Veeqo for WooCommerce versions 2.2.8 and earlier are affected. A Subscriber-level or higher WordPress user can cause the bridge installer to retrieve and unpack an attacker-controlled archive in the WordPress root, potentially placing PHP files there. Exploitation requires an authenticated low-privilege account.",
  "mitigation": "Deactivate and remove the plugin where it is not required, and restrict or revoke untrusted Subscriber-level accounts. No fixed release is documented; keep the plugin disabled until a vendor update is available.",
  "vendor": null,
  "product": "Veeqo for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.2.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Veeqo for WooCommerce",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 4.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
  "epss_score": 0.0018,
  "epss_percentile": 0.0676,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.00956335,
  "t0_at": "2026-10-11T06:00:19.300000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-20T02:55:45.729237+00:00",
      "days": 8.871833671724538,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:19.300000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-11T06:00:19.300000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:19.300000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-93550"
    }
  }
}

published 2026-10-18 19:37Z
last change 2026-10-21 00:18Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.