CVE-2026-14307

validatedZero produced an exploit or a check.

GHSA-xg5h-jcfm-24g6 ↗EUVD-2026-68155 ↗

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).+0mkevAttacks confirmed in the real world.+77d
GeotargetingWP Geotargeting WP < 3.5.6.2
fixed in 3.5.6.2
ETK-2026-4522Zero's internal tracking ID, independent of the CVE number., permanent identifier
+77dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
cve.org publicationpublic poc+0dtrigger signal +77dkev+77dcheck availableagent stopped
0
+20d
+40d
+60d

description

GeotargetingWP versions before 3.5.6.2 are affected by reflected cross-site scripting in certain AJAX responses. An unauthenticated attacker may cause browser-side script execution if they can persuade a victim to submit a malicious request.

mitigation

Upgrade GeotargetingWP to version 3.5.6.2 or later. Until upgraded, reduce exposure by limiting access to affected WordPress AJAX endpoints where operationally feasible.

fixed in 3.5.6.2

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.28%20th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-30 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+0m
Δ to kevAttacks confirmed in the real world.
+77d

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-08-30 06:00Z
  2. 2026-11-15
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-15 00:00Z
  4. 2026-11-15 15:16Z
  5. 2026-11-15 15:28Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4522",
  "cve_id": "CVE-2026-14307",
  "display_id": "CVE-2026-14307",
  "ghsa_id": "GHSA-xg5h-jcfm-24g6",
  "euvd_id": "EUVD-2026-68155",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Reflected cross-site scripting in GeotargetingWP",
  "summary": "GeotargetingWP versions before 3.5.6.2 are affected by reflected cross-site scripting in certain AJAX responses. An unauthenticated attacker may cause browser-side script execution if they can persuade a victim to submit a malicious request.",
  "mitigation": "Upgrade GeotargetingWP to version 3.5.6.2 or later. Until upgraded, reduce exposure by limiting access to affected WordPress AJAX endpoints where operationally feasible.",
  "vendor": "GeotargetingWP",
  "product": "Geotargeting WP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.5.6.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.5.6.2"
      ],
      "package_name": "geotargetingwp",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.1,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
  "epss_score": 0.0028,
  "epss_percentile": 0.2094,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.01145305,
  "t0_at": "2026-08-30T06:00:18.078000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-15T15:16:57.553899+00:00",
      "days": 77.38656800809028,
      "is_lower_bound": false,
      "measured_at": "2026-08-30T06:00:18.078000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-15T00:00:00+00:00",
      "days": 77,
      "is_lower_bound": false,
      "measured_at": "2026-08-30T06:00:18.078000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-14307"
    },
    "public_poc": {
      "at": "2026-08-30T06:00:18.078000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-08-30T06:00:18.078000+00:00",
      "url": "https://wpscan.com/vulnerability/5f55b592-9113-47d1-8b48-6ba785c0834a/"
    },
    "trigger_signal": {
      "at": "2026-11-15T00:00:00+00:00",
      "days": 76.74979076388888,
      "is_lower_bound": false,
      "measured_at": "2026-08-30T06:00:18.078000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-14307"
    }
  }
}

published 2026-11-15 15:16Z
last change 2026-11-18 21:43Z

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.