CVE-2026-106470

validatedZero produced an exploit or a check.

GHSA-jmr2-v244-x8cp ↗EUVD-2026-103256 ↗

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.
WP Data Access < 5.5.88
fixed in 5.5.88
ETK-2026-2431Zero's internal tracking ID, independent of the CVE number., permanent identifier
+5.2dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+5.2dagent stopped
0
+1d
+2d
+3d
+4d

description

WP Data Access versions earlier than 5.5.88 are affected by an authorization and request-forgery protection gap. An authenticated user, including a subscriber-level user, may cause the WordPress server to connect to selected network hosts and ports, including internal services, and observe the connection result.

mitigation

Upgrade WP Data Access to version 5.5.88 or later. Restrict untrusted user accounts until the update is deployed.

fixed in 5.5.88

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-17 06:00Z
Δ 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

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-17 06:00Z
    cve_org: trigger signal, started the run
  2. 2026-10-22 11:49Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2431",
  "cve_id": "CVE-2026-106470",
  "display_id": "CVE-2026-106470",
  "ghsa_id": "GHSA-jmr2-v244-x8cp",
  "euvd_id": "EUVD-2026-103256",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated server-side request forgery in WP Data Access",
  "summary": "WP Data Access versions earlier than 5.5.88 are affected by an authorization and request-forgery protection gap. An authenticated user, including a subscriber-level user, may cause the WordPress server to connect to selected network hosts and ports, including internal services, and observe the connection result.",
  "mitigation": "Upgrade WP Data Access to version 5.5.88 or later. Restrict untrusted user accounts until the update is deployed.",
  "vendor": null,
  "product": "WP Data Access",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.5.88"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.5.88"
      ],
      "package_name": "WP Data Access",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.011275883333333334,
  "t0_at": "2026-10-17T06:00:13.602000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-22T11:49:30.803155+00:00",
      "days": 5.242560198553241,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T06:00:13.602000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-17T06:00:13.602000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T06:00:13.602000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106470"
    }
  }
}

published 2026-10-22 11:49Z
last change 2026-10-22 12:53Z

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.