CVE-2026-18789

validatedZero produced an exploit or a check.

GHSA-fh54-f94w-q4hw ↗EUVD-2026-57102 ↗

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.+71d
Ezoic >= 2.6.35, < 2.23.1
fixed in 2.23.1
ETK-2026-2541Zero's internal tracking ID, independent of the CVE number., permanent identifier
+73dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−71dpublic poctrigger signal +0dkev+1.0dcheck available+2.6dagent stopped
−60d
−40d
−20d

description

Ezoic WordPress plugin versions before 2.23.1 inadequately protect parts of the content-export capability. An unauthenticated remote attacker can obtain a server-generated database export containing password hashes and reset tokens, and may modify some plugin settings. Exploitation requires an affected plugin version to be reachable by the attacker.

mitigation

Update the Ezoic WordPress plugin to version 2.23.1 or later. Until it is updated, restrict public access to the affected WordPress site where feasible.

fixed in 2.23.1

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.41%33rd percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-12 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.
+71d

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-08-12 06:00Z
  2. 2026-10-22
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-22 00:00Z
  4. 2026-10-24 13:52Z
  5. 2026-10-24 14:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2541",
  "cve_id": "CVE-2026-18789",
  "display_id": "CVE-2026-18789",
  "ghsa_id": "GHSA-fh54-f94w-q4hw",
  "euvd_id": "EUVD-2026-57102",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in the Ezoic WordPress plugin",
  "summary": "Ezoic WordPress plugin versions before 2.23.1 inadequately protect parts of the content-export capability. An unauthenticated remote attacker can obtain a server-generated database export containing password hashes and reset tokens, and may modify some plugin settings. Exploitation requires an affected plugin version to be reachable by the attacker.",
  "mitigation": "Update the Ezoic WordPress plugin to version 2.23.1 or later. Until it is updated, restrict public access to the affected WordPress site where feasible.",
  "vendor": "Ezoic",
  "product": "Ezoic",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.6.35, < 2.23.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.23.1"
      ],
      "package_name": "Ezoic",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0041,
  "epss_percentile": 0.3382,
  "epss_asof": "2026-10-23",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.0098554,
  "t0_at": "2026-08-12T06:00:17.906000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-24T13:52:02.652691+00:00",
      "days": 73.32760123484954,
      "is_lower_bound": false,
      "measured_at": "2026-08-12T06:00:17.906000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-22T00:00:00+00:00",
      "days": 71,
      "is_lower_bound": false,
      "measured_at": "2026-08-12T06:00:17.906000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-18789"
    },
    "public_poc": {
      "at": "2026-08-12T06:00:17.906000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-08-12T06:00:17.906000+00:00",
      "url": "https://wpscan.com/vulnerability/1e2ce237-dc91-4144-875a-339b5ea05f3a/"
    },
    "trigger_signal": {
      "at": "2026-10-22T00:00:00+00:00",
      "days": 70.74979275462962,
      "is_lower_bound": false,
      "measured_at": "2026-08-12T06:00:17.906000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-18789"
    }
  }
}

published 2026-10-24 13:51Z
last change 2026-10-24 18:43Z

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.