CVE-2026-110009

validatedZero produced an exploit or a check.

GHSA-cq6v-qcf9-9mf3 ↗EUVD-2026-128851 ↗

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.
unzerplugins Unzer Payments <= 2.2.1
CWE-287 Improper Authentication
ETK-2026-4801Zero's internal tracking ID, independent of the CVE number., permanent identifier
+14mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+14magent stopped
0
+5min
+10min
+15min

description

Unzer Payments for WordPress versions through 2.2.1 can allow an unauthenticated remote requester to obtain a session as an existing site user, potentially including an administrator. Exploitation requires the Google Pay Express Checkout endpoint to be reachable and knowledge of an account email address.

mitigation

Block external access to the Google Pay Express Checkout wc-api endpoint or disable that checkout integration until the vendor provides an update. Review active WordPress sessions and administrator accounts for unexpected access.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 13:32Z
Δ 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-11-18 13:32Z
    cve_org: trigger signal, started the run
  2. 2026-11-18 13:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4801",
  "cve_id": "CVE-2026-110009",
  "display_id": "CVE-2026-110009",
  "ghsa_id": "GHSA-cq6v-qcf9-9mf3",
  "euvd_id": "EUVD-2026-128851",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Unzer Payments for WordPress",
  "summary": "Unzer Payments for WordPress versions through 2.2.1 can allow an unauthenticated remote requester to obtain a session as an existing site user, potentially including an administrator. Exploitation requires the Google Pay Express Checkout endpoint to be reachable and knowledge of an account email address.",
  "mitigation": "Block external access to the Google Pay Express Checkout wc-api endpoint or disable that checkout integration until the vendor provides an update. Review active WordPress sessions and administrator accounts for unexpected access.",
  "vendor": "unzerplugins",
  "product": "Unzer Payments",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.2.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Unzer Payments",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.012540316666666667,
  "t0_at": "2026-11-18T13:32:27.486000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-18T13:46:03.797347+00:00",
      "days": 0.009448047997685186,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T13:32:27.486000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-18T13:32:27.486000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T13:32:27.486000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110009"
    }
  }
}

published 2026-11-18 13:45Z
last change 2026-11-18 20:02Z

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.