CVE-2026-85705

validatedZero produced an exploit or a check.

GHSA-jvcr-7q46-jqm3 ↗EUVD-2026-82763 ↗

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.+59d
AyeCode Ltd Location Manager <= 2.3.38
ETK-2026-4596Zero's internal tracking ID, independent of the CVE number., permanent identifier
+59dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
cve.org publicationtrigger signal +59dkev+59dcheck availableagent stopped
0
+20d
+40d

description

Location Manager for WordPress through version 2.3.38 is affected by an SQL injection flaw in location-related REST API handling. An unauthenticated remote attacker may manipulate affected public endpoints to query sensitive information from the WordPress database. Exposure requires the affected REST endpoints to be publicly reachable.

mitigation

Update Location Manager when a vendor-fixed release becomes available; no fixed version is recorded. Until then, restrict public access to the affected location REST endpoints or disable the plugin if those endpoints are not required.

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.46%40th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-18 07:40Z
Δ 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.
+59d

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-09-18 07:40Z
  2. 2026-11-16
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-16 00:00Z
  4. 2026-11-16 15:49Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4596",
  "cve_id": "CVE-2026-85705",
  "display_id": "CVE-2026-85705",
  "ghsa_id": "GHSA-jvcr-7q46-jqm3",
  "euvd_id": "EUVD-2026-82763",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in Location Manager",
  "summary": "Location Manager for WordPress through version 2.3.38 is affected by an SQL injection flaw in location-related REST API handling. An unauthenticated remote attacker may manipulate affected public endpoints to query sensitive information from the WordPress database. Exposure requires the affected REST endpoints to be publicly reachable.",
  "mitigation": "Update Location Manager when a vendor-fixed release becomes available; no fixed version is recorded. Until then, restrict public access to the affected location REST endpoints or disable the plugin if those endpoints are not required.",
  "vendor": "AyeCode Ltd",
  "product": "Location Manager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.3.38"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Location Manager",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0046,
  "epss_percentile": 0.4066,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.011574866666666666,
  "t0_at": "2026-09-18T07:40:05.690000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-16T15:49:45.978169+00:00",
      "days": 59.34004963158565,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T07:40:05.690000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-16T00:00:00+00:00",
      "days": 59,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T07:40:05.690000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-85705"
    },
    "trigger_signal": {
      "at": "2026-11-16T00:00:00+00:00",
      "days": 58.68048969907407,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T07:40:05.690000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-85705"
    }
  }
}

published 2026-11-16 15:49Z
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.