CVE-2026-123696

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

GHSA-f6p5-3fqv-xhh4 ↗EUVD-2026-123200 ↗

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.
Security For WooCommerce <= 1.0.16
ETK-2026-4144Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 44msince last run
40mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h12m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Security For WooCommerce through version 1.0.16 permits two-factor enrollment resets without verifying authorization. An unauthenticated attacker who can reach an affected WordPress site could disable two-factor protection for selected accounts or broadly across the site.

mitigation

Disable the plugin or restrict untrusted access to the affected WordPress site until a vendor update is available. No fixed version is recorded in the advisory; monitor for and apply a vendor-provided fix promptly.

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-11 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4144",
  "cve_id": "CVE-2026-123696",
  "display_id": "CVE-2026-123696",
  "ghsa_id": "GHSA-f6p5-3fqv-xhh4",
  "euvd_id": "EUVD-2026-123200",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated two-factor reset in Security For WooCommerce",
  "summary": "Security For WooCommerce through version 1.0.16 permits two-factor enrollment resets without verifying authorization. An unauthenticated attacker who can reach an affected WordPress site could disable two-factor protection for selected accounts or broadly across the site.",
  "mitigation": "Disable the plugin or restrict untrusted access to the affected WordPress site until a vendor update is available. No fixed version is recorded in the advisory; monitor for and apply a vendor-provided fix promptly.",
  "vendor": null,
  "product": "Security For WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.16"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Security For WooCommerce",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 40.35911806666667,
  "t0_at": "2026-11-11T06:00:14.221000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T06:00:14.221000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T06:00:14.221000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123696"
    }
  }
}

published 2026-11-11 06:31Z
last change 2026-11-11 08:31Z

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.