CVE-2026-103913

validatedZero produced an exploit or a check.

GHSA-285m-c668-wj9h ↗EUVD-2026-91921 ↗

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.
paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory <= 2.8.186
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-425, permanent identifier
+1h41mTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+101magent stopped
0
+30min
+60min
+90min

description

GeoDirectory for WordPress through version 2.8.186 mishandles coordinate values saved with directory listings. An authenticated user with Subscriber-level access or higher may use a crafted listing to cause database queries to expose sensitive information when affected public distance-sorted listing functionality is used.

mitigation

Restrict untrusted users from creating or editing directory listings, and disable public distance-sorted listing searches where feasible. Monitor the vendor's updates and upgrade promptly when a fixed release is published.

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.38%31st percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 05:29Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-03 05:29Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-425",
  "cve_id": "CVE-2026-103913",
  "display_id": "CVE-2026-103913",
  "ghsa_id": "GHSA-285m-c668-wj9h",
  "euvd_id": "EUVD-2026-91921",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in the GeoDirectory WordPress plugin",
  "summary": "GeoDirectory for WordPress through version 2.8.186 mishandles coordinate values saved with directory listings. An authenticated user with Subscriber-level access or higher may use a crafted listing to cause database queries to expose sensitive information when affected public distance-sorted listing functionality is used.",
  "mitigation": "Restrict untrusted users from creating or editing directory listings, and disable public distance-sorted listing searches where feasible. Monitor the vendor's updates and upgrade promptly when a fixed release is published.",
  "vendor": "paoltaia",
  "product": "GeoDirectory – WP Business Directory Plugin and Classified Listings Directory",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.8.186"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GeoDirectory – WP Business Directory Plugin and Classified Listings Directory",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0038,
  "epss_percentile": 0.3105,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 24.147994466666667,
  "t0_at": "2026-10-03T05:29:14.418000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T07:10:14.937944+00:00",
      "days": 0.07014490675925926,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T05:29:14.418000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-03T05:29:14.418000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T05:29:14.418000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103913"
    }
  }
}

published 2026-10-03 06:46Z
last change 2026-10-21 18:33Z

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.