CVE-2026-89299

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

GHSA-mm7c-7mwq-mppr ↗EUVD-2026-96789 ↗

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.
WP Verify API <= 1.0.0
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1934Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 17h 44msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+167h36m
0
+2h
+4h
+6h
+8h
+10h

description

WP Verify API WordPress plugin versions through 1.0.0 are affected by an SQL injection vulnerability. An unauthenticated remote attacker may manipulate a parameter used in a database query. Exploitation requires the vulnerable plugin to be installed and reachable.

mitigation

Update WP Verify API to a vendor release newer than 1.0.0 when one is available. Until then, disable the plugin or restrict access to endpoints it exposes.

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.
contextual
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.26%17th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-11 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-11 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1934",
  "cve_id": "CVE-2026-89299",
  "display_id": "CVE-2026-89299",
  "ghsa_id": "GHSA-mm7c-7mwq-mppr",
  "euvd_id": "EUVD-2026-96789",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in WP Verify API",
  "summary": "WP Verify API WordPress plugin versions through 1.0.0 are affected by an SQL injection vulnerability. An unauthenticated remote attacker may manipulate a parameter used in a database query. Exploitation requires the vulnerable plugin to be installed and reachable.",
  "mitigation": "Update WP Verify API to a vendor release newer than 1.0.0 when one is available. Until then, disable the plugin or restrict access to endpoints it exposes.",
  "vendor": null,
  "product": "WP Verify API",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WP Verify API",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.6,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": 0.0026,
  "epss_percentile": 0.1706,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.06075155,
  "t0_at": "2026-10-11T06:00:18.426000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T06:00:18.426000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:18.426000+00:00",
      "url": "https://github.com/advisories/GHSA-mm7c-7mwq-mppr"
    }
  }
}

published 2026-10-18 05:25Z
last change 2026-10-21 21:36Z

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.