CVE-2026-118267

validatedZero produced an exploit or a check.

GHSA-v86c-jgq8-6hrh ↗EUVD-2026-119157 ↗

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.0d
wpdataaccess WP Data Access <= 5.5.89
ETK-2026-3851Zero's internal tracking ID, independent of the CVE number., permanent identifier
+5h39mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal −11h27mcve.org publicationkev+0hcheck available+5h39magent stopped
−6h

description

WP Data Access through version 5.5.89 can allow write requests to bypass Data App row and column restrictions. An attacker may modify protected WordPress data and obtain administrative control when a published Data App permits update, delete, or insert operations for subscriber or anonymous users.

mitigation

Disable update, delete, and insert transactions on Data Apps accessible to subscriber or anonymous users, or limit those apps to trusted administrators. Review published Data Apps for anonymous authorization and remove it where it is 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.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-07 11:26Z
Δ 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.
0d

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-11-07
    vulncheck_kev: trigger signal, started the run
  2. 2026-11-07 00:00Z
  3. 2026-11-07 11:26Z
  4. 2026-11-07 17:05Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3851",
  "cve_id": "CVE-2026-118267",
  "display_id": "CVE-2026-118267",
  "ghsa_id": "GHSA-v86c-jgq8-6hrh",
  "euvd_id": "EUVD-2026-119157",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in WP Data Access write operations",
  "summary": "WP Data Access through version 5.5.89 can allow write requests to bypass Data App row and column restrictions. An attacker may modify protected WordPress data and obtain administrative control when a published Data App permits update, delete, or insert operations for subscriber or anonymous users.",
  "mitigation": "Disable update, delete, and insert transactions on Data Apps accessible to subscriber or anonymous users, or limit those apps to trusted administrators. Review published Data Apps for anonymous authorization and remove it where it is not required.",
  "vendor": "wpdataaccess",
  "product": "WP Data Access",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 5.5.89"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.011031816666666666,
  "t0_at": "2026-11-07T11:26:32.742000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-07T17:05:35.116785+00:00",
      "days": 0.23544415260416668,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T11:26:32.742000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-07T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T11:26:32.742000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-118267"
    },
    "trigger_signal": {
      "at": "2026-11-07T00:00:00+00:00",
      "days": -0.4767678472222222,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T11:26:32.742000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-118267"
    }
  }
}

published 2026-11-07 17:05Z
last change 2026-11-08 00:40Z

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.