CVE-2026-62097

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

GHSA-m7v8-vw7r-3w9f ↗EUVD-2026-89957 ↗

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.
WPTasty Business Directory <= 6.4.27
ETK-2026-171, permanent identifier
20d 07h 26msince last run
40mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+10h30m
0
+2h
+4h
+6h
+8h
+12h

description

Business Directory versions up to and including 6.4.27 are affected by a blind SQL injection flaw. An authenticated attacker with high-level privileges may be able to influence database queries through the plugin.

mitigation

Update Business Directory to a release newer than 6.4.27 after confirming the vendor's remediation guidance. Until then, disable the plugin where feasible and restrict high-privilege WordPress accounts to trusted administrators.

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%12th percentile
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 14:02Z
Δ 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-09-30 14:02Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 14:02Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-171",
  "cve_id": "CVE-2026-62097",
  "display_id": "CVE-2026-62097",
  "ghsa_id": "GHSA-m7v8-vw7r-3w9f",
  "euvd_id": "EUVD-2026-89957",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Blind SQL injection in Business Directory",
  "summary": "Business Directory versions up to and including 6.4.27 are affected by a blind SQL injection flaw. An authenticated attacker with high-level privileges may be able to influence database queries through the plugin.",
  "mitigation": "Update Business Directory to a release newer than 6.4.27 after confirming the vendor's remediation guidance. Until then, disable the plugin where feasible and restrict high-privilege WordPress accounts to trusted administrators.",
  "vendor": "WPTasty",
  "product": "Business Directory",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 6.4.27"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "business-directory-plugin",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L",
  "epss_score": 0.0023,
  "epss_percentile": 0.1253,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 40.49763376666667,
  "t0_at": "2026-09-30T14:02:22.503000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T14:02:22.503000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T14:02:22.503000+00:00",
      "url": "https://github.com/advisories/GHSA-m7v8-vw7r-3w9f"
    }
  }
}

published 2026-09-30 23:52Z
last change 2026-10-21 05:31Z

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.