CVE-2026-13389

validatedZero produced an exploit or a check.

GHSA-xw6w-vrqp-fhq4 ↗EUVD-2026-51952 ↗

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).+0mkevAttacks confirmed in the real world.+72d
webtoffee-cookie-consent < 3.5.3
fixed in 3.5.3
ETK-2026-1952Zero's internal tracking ID, independent of the CVE number., permanent identifier
+77dTTV
33mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−72dpublic poctrigger signal +0dkev+1.0dcheck available+5.4dagent stopped
−60d
−40d
−20d

description

webtoffee-cookie-consent versions before 3.5.3 expose REST API functions without adequate access control. An unauthenticated remote attacker may read or delete stored consent records, create WordPress posts, or change the plugin licensing state when an affected plugin is reachable.

mitigation

Update webtoffee-cookie-consent to version 3.5.3 or later. Until the update is complete, restrict unauthenticated access to the affected REST API routes where feasible.

fixed in 3.5.3

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.
0.30%21st percentile
agent run time
33m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-02 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+0m
Δ to kevAttacks confirmed in the real world.
+72d

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-08-02 06:00Z
  2. 2026-10-13
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-13 00:00Z
  4. 2026-10-18 08:55Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1952",
  "cve_id": "CVE-2026-13389",
  "display_id": "CVE-2026-13389",
  "ghsa_id": "GHSA-xw6w-vrqp-fhq4",
  "euvd_id": "EUVD-2026-51952",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing REST API authorization in webtoffee-cookie-consent",
  "summary": "webtoffee-cookie-consent versions before 3.5.3 expose REST API functions without adequate access control. An unauthenticated remote attacker may read or delete stored consent records, create WordPress posts, or change the plugin licensing state when an affected plugin is reachable.",
  "mitigation": "Update webtoffee-cookie-consent to version 3.5.3 or later. Until the update is complete, restrict unauthenticated access to the affected REST API routes where feasible.",
  "vendor": null,
  "product": "webtoffee-cookie-consent",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.5.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.5.3"
      ],
      "package_name": "webtoffee-cookie-consent",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 6.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
  "epss_score": 0.003,
  "epss_percentile": 0.2125,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 32.6845549,
  "t0_at": "2026-08-02T06:00:13.865000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-18T09:00:45.112863+00:00",
      "days": 77.12536166508102,
      "is_lower_bound": false,
      "measured_at": "2026-08-02T06:00:13.865000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-13T00:00:00+00:00",
      "days": 72,
      "is_lower_bound": false,
      "measured_at": "2026-08-02T06:00:13.865000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-13389"
    },
    "public_poc": {
      "at": "2026-08-02T06:00:13.865000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-08-02T06:00:13.865000+00:00",
      "url": "https://wpscan.com/vulnerability/a591c79d-5db7-4716-8b6c-004b1195edf7/"
    },
    "trigger_signal": {
      "at": "2026-10-13T00:00:00+00:00",
      "days": 71.74983952546296,
      "is_lower_bound": false,
      "measured_at": "2026-08-02T06:00:13.865000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-13389"
    }
  }
}

published 2026-10-18 08:28Z
last change 2026-10-21 10:52Z

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.