CVE-2026-123145

validatedZero produced an exploit or a check.

GHSA-6hgw-83cf-5q96 ↗EUVD-2026-119834 ↗

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.
WooCommerce Stripe Payment Gateway >= 10.9.0, < 11.1.0
fixed in 11.1.0
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-3932Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h39mTTV
37mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+99magent stopped
0
+30min
+60min
+90min

description

WooCommerce Stripe Payment Gateway releases before 11.1.0 can retain passwords chosen during express checkout account creation as unencrypted order metadata. Anyone who can access the affected order records or underlying database may be able to obtain those passwords; exposure requires that an account was created through the affected checkout flow.

mitigation

Upgrade WooCommerce Stripe Payment Gateway to version 11.1.0, which removes the retained password data during update. Reset passwords for accounts that may have been created through the affected checkout flow.

fixed in 11.1.0

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.14%3rd percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3932",
  "cve_id": "CVE-2026-123145",
  "display_id": "CVE-2026-123145",
  "ghsa_id": "GHSA-6hgw-83cf-5q96",
  "euvd_id": "EUVD-2026-119834",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Plaintext password storage in WooCommerce Stripe Payment Gateway",
  "summary": "WooCommerce Stripe Payment Gateway releases before 11.1.0 can retain passwords chosen during express checkout account creation as unencrypted order metadata. Anyone who can access the affected order records or underlying database may be able to obtain those passwords; exposure requires that an account was created through the affected checkout flow.",
  "mitigation": "Upgrade WooCommerce Stripe Payment Gateway to version 11.1.0, which removes the retained password data during update. Reset passwords for accounts that may have been created through the affected checkout flow.",
  "vendor": null,
  "product": "WooCommerce Stripe Payment Gateway",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.9.0, < 11.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "11.1.0"
      ],
      "package_name": "WooCommerce Stripe Payment Gateway",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 4.4,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0014,
  "epss_percentile": 0.0335,
  "epss_asof": "2026-11-09",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 37.127433366666665,
  "t0_at": "2026-11-09T06:00:28.964000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-09T07:39:43.300048+00:00",
      "days": 0.06891592648148148,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T06:00:28.964000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-09T06:00:28.964000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T06:00:28.964000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123145"
    }
  }
}

published 2026-11-09 07:02Z
last change 2026-11-11 05:47Z

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.