CVE-2026-118635

validatedZero produced an exploit or a check.

GHSA-8px6-jx7m-vf9q ↗EUVD-2026-114219 ↗

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.+15d
paoltaia GeoDirectory <= 2.8.198
ETK-2026-4477Zero's internal tracking ID, independent of the CVE number., permanent identifier
+15dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−14dtrigger signal +0dcheck available+0.7dkev+1.0dagent stopped
−10d
−5d
0

description

GeoDirectory for WordPress is affected in versions through 2.8.198. An unauthenticated remote attacker can cause arbitrary WordPress shortcodes to be executed when the vulnerable plugin functionality is reachable; no login is required.

mitigation

Disable GeoDirectory on publicly accessible sites until a vendor update addressing this issue is confirmed. If it must remain enabled, restrict public access to the affected WordPress site or vulnerable functionality where operationally possible.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.44%38th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 17:15Z
Δ 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.
+15d

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-30 17:15Z
  2. 2026-11-14
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-14 00:00Z
  4. 2026-11-14 16:48Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4477",
  "cve_id": "CVE-2026-118635",
  "display_id": "CVE-2026-118635",
  "ghsa_id": "GHSA-8px6-jx7m-vf9q",
  "euvd_id": "EUVD-2026-114219",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated shortcode execution in GeoDirectory",
  "summary": "GeoDirectory for WordPress is affected in versions through 2.8.198. An unauthenticated remote attacker can cause arbitrary WordPress shortcodes to be executed when the vulnerable plugin functionality is reachable; no login is required.",
  "mitigation": "Disable GeoDirectory on publicly accessible sites until a vendor update addressing this issue is confirmed. If it must remain enabled, restrict public access to the affected WordPress site or vulnerable functionality where operationally possible.",
  "vendor": "paoltaia",
  "product": "GeoDirectory",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.8.198"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GeoDirectory – WP Business Directory Plugin and Classified Listings Directory",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 6.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
  "epss_score": 0.0044,
  "epss_percentile": 0.3837,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.00983225,
  "t0_at": "2026-10-30T17:15:27.562000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-14T16:48:00.169457+00:00",
      "days": 14.98093295667824,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T17:15:27.562000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-14T00:00:00+00:00",
      "days": 15,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T17:15:27.562000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-118635"
    },
    "trigger_signal": {
      "at": "2026-11-14T00:00:00+00:00",
      "days": 14.28093099537037,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T17:15:27.562000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-118635"
    }
  }
}

published 2026-11-14 16:47Z
last change 2026-11-18 21:29Z

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.