CVE-2026-115257

validatedZero produced an exploit or a check.

GHSA-p54f-4qj5-25h3 ↗EUVD-2026-116729 ↗

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 Roster < 2.36
fixed in 2.36
ETK-2026-3479Zero's internal tracking ID, independent of the CVE number., permanent identifier
+3h21mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+3h21magent stopped
0
+1h
+2h
+3h

description

WP Roster versions before 2.36 allow roster data to be changed without authentication. An attacker able to reach an affected WordPress site can alter, erase, or restore roster entries because update requests are not access-controlled.

mitigation

Update WP Roster to version 2.36 or later. Until updating, restrict public access to affected WordPress sites where feasible.

fixed in 2.36

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-11-04 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-11-04 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-04 06:00Z
  3. 2026-11-04 09:21Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3479",
  "cve_id": "CVE-2026-115257",
  "display_id": "CVE-2026-115257",
  "ghsa_id": "GHSA-p54f-4qj5-25h3",
  "euvd_id": "EUVD-2026-116729",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization for roster updates in WP Roster",
  "summary": "WP Roster versions before 2.36 allow roster data to be changed without authentication. An attacker able to reach an affected WordPress site can alter, erase, or restore roster entries because update requests are not access-controlled.",
  "mitigation": "Update WP Roster to version 2.36 or later. Until updating, restrict public access to affected WordPress sites where feasible.",
  "vendor": null,
  "product": "WP Roster",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.36"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.36"
      ],
      "package_name": "WP Roster",
      "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.013129633333333333,
  "t0_at": "2026-11-04T06:00:27.201000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-04T09:21:11.804712+00:00",
      "days": 0.13940513555555556,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T06:00:27.201000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-04T06:00:27.201000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T06:00:27.201000+00:00",
      "url": "https://github.com/advisories/GHSA-p54f-4qj5-25h3"
    }
  }
}

published 2026-11-04 09:21Z
last change 2026-11-04 12:27Z

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.