CVE-2026-89304

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

GHSA-3p92-g8x8-w3r5 ↗EUVD-2026-96791 ↗

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

description

Paymendo WordPress plugin versions through 1.1 are affected by an SQL injection flaw. An unauthenticated attacker may perform blind database queries when the vulnerable plugin functionality is reachable.

mitigation

Update Paymendo to a release later than 1.1 if the vendor has published and verified one. Until then, disable the plugin or restrict access to the affected functionality to reduce exposure.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%13th percentile
agent run time
26m
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-89304

{
  "etk_id": "ETK-2026-1932",
  "cve_id": "CVE-2026-89304",
  "display_id": "CVE-2026-89304",
  "ghsa_id": "GHSA-3p92-g8x8-w3r5",
  "euvd_id": "EUVD-2026-96791",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in Paymendo WordPress plugin",
  "summary": "Paymendo WordPress plugin versions through 1.1 are affected by an SQL injection flaw. An unauthenticated attacker may perform blind database queries when the vulnerable plugin functionality is reachable.",
  "mitigation": "Update Paymendo to a release later than 1.1 if the vendor has published and verified one. Until then, disable the plugin or restrict access to the affected functionality to reduce exposure.",
  "vendor": null,
  "product": "paymendo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "paymendo",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 6.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1351,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.289246,
  "t0_at": "2026-10-11T06:00:18.778000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T06:00:18.778000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:18.778000+00:00",
      "url": "https://github.com/advisories/GHSA-3p92-g8x8-w3r5"
    }
  }
}

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

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.