CVE-2026-89302

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

GHSA-xwx7-jj6g-vhp6 ↗EUVD-2026-96790 ↗

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.
Post Voting System <= 1.0
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1933Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 06h 36msince last run
1h 38mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+169h01m
0
+2h
+4h
+6h
+8h
+10h

description

Post Voting System for WordPress is affected through version 1.0. An unauthenticated remote attacker may manipulate database queries through the plugin; no prior account or user interaction is required.

mitigation

Disable and remove the Post Voting System plugin from affected WordPress sites until a vendor-fixed release is available. Limit public access to affected sites where immediate removal is not possible.

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.
–
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%16th percentile
agent run time
1h 38m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

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-89302

{
  "etk_id": "ETK-2026-1933",
  "cve_id": "CVE-2026-89302",
  "display_id": "CVE-2026-89302",
  "ghsa_id": "GHSA-xwx7-jj6g-vhp6",
  "euvd_id": "EUVD-2026-96790",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in Post Voting System",
  "summary": "Post Voting System for WordPress is affected through version 1.0. An unauthenticated remote attacker may manipulate database queries through the plugin; no prior account or user interaction is required.",
  "mitigation": "Disable and remove the Post Voting System plugin from affected WordPress sites until a vendor-fixed release is available. Limit public access to affected sites where immediate removal is not possible.",
  "vendor": null,
  "product": "Post Voting System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Post Voting System",
      "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.1697,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 97.7327057,
  "t0_at": "2026-10-11T06:00:18.600000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T06:00:18.600000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:18.600000+00:00",
      "url": "https://github.com/advisories/GHSA-xwx7-jj6g-vhp6"
    }
  }
}

published 2026-10-18 05:23Z
last change 2026-10-21 04:45Z

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.