CVE-2026-120558

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

GHSA-cm75-3jj2-f2gr ↗EUVD-2026-115663 ↗

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.
zorem Advanced Shipment Tracking for WooCommerce <= 3.9
ETK-2026-3358Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 15msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+5h46m
0
+2h
+4h
+8h
+10h
+12h

description

Advanced Shipment Tracking for WooCommerce versions through 3.9 mishandle a shipment-tracking request parameter. An authenticated user with Shop Manager-level access or higher could use the flaw to access or alter database data.

mitigation

Disable the plugin or restrict its shipment-tracking REST endpoint until an updated release is confirmed to address the issue. Remove Shop Manager access from untrusted accounts and review accounts holding that role.

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 04:43Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-03 04:43Z
    ghsa: trigger signal, started the run
  2. 2026-11-03 04:43Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3358",
  "cve_id": "CVE-2026-120558",
  "display_id": "CVE-2026-120558",
  "ghsa_id": "GHSA-cm75-3jj2-f2gr",
  "euvd_id": "EUVD-2026-115663",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Advanced Shipment Tracking for WooCommerce",
  "summary": "Advanced Shipment Tracking for WooCommerce versions through 3.9 mishandle a shipment-tracking request parameter. An authenticated user with Shop Manager-level access or higher could use the flaw to access or alter database data.",
  "mitigation": "Disable the plugin or restrict its shipment-tracking REST endpoint until an updated release is confirmed to address the issue. Remove Shop Manager access from untrusted accounts and review accounts holding that role.",
  "vendor": "zorem",
  "product": "Advanced Shipment Tracking for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.9"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Advanced Shipment Tracking for WooCommerce",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.858265033333332,
  "t0_at": "2026-11-03T04:43:07.675000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T04:43:07.675000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T04:43:07.675000+00:00",
      "url": "https://github.com/advisories/GHSA-cm75-3jj2-f2gr"
    }
  }
}

published 2026-11-03 10:03Z
last change 2026-11-03 12:23Z

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.