CVE-2026-89305

validatedZero produced an exploit or a check.

GHSA-cc47-x7cq-5www ↗EUVD-2026-96792 ↗

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).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-2246Zero's internal tracking ID, independent of the CVE number., permanent identifier
+9.8dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+9.8dagent stopped
0
+2d
+4d
+6d
+8d

description

Paymendo WordPress plugin versions through 1.1 are affected by SQL injection. An authenticated attacker may influence database queries through an insufficiently handled parameter.

mitigation

Update to a vendor-confirmed fixed release when one is available. Until then, disable the plugin or limit access to trusted authenticated users.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
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

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-10-11 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-11 06:00Z
  3. 2026-10-21 00:23Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2246",
  "cve_id": "CVE-2026-89305",
  "display_id": "CVE-2026-89305",
  "ghsa_id": "GHSA-cc47-x7cq-5www",
  "euvd_id": "EUVD-2026-96792",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in paymendo WordPress plugin",
  "summary": "Paymendo WordPress plugin versions through 1.1 are affected by SQL injection. An authenticated attacker may influence database queries through an insufficiently handled parameter.",
  "mitigation": "Update to a vendor-confirmed fixed release when one is available. Until then, disable the plugin or limit access to trusted authenticated users.",
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.012185233333333333,
  "t0_at": "2026-10-11T06:00:18.955000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-21T00:23:37.458020+00:00",
      "days": 9.766186377546296,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:18.955000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-11T06:00:18.955000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T06:00:18.955000+00:00",
      "url": "https://github.com/advisories/GHSA-cc47-x7cq-5www"
    }
  }
}

published 2026-10-21 00:23Z
last change 2026-10-21 05:00Z

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.