CVE-2026-115255

waiting for further signalsZero needs more public information before it can validate it.

GHSA-j835-2vx3-j669 ↗EUVD-2026-111731 ↗

no check availablenot proven exploitable
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.35
fixed in 2.35
ETK-2026-2840Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 10msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h55m
0
+4h
+6h
+8h
+10h
+12h

description

WP Roster versions before 2.35 are affected by missing authorization and nonce validation in an AJAX action. An unauthenticated attacker can delete WordPress user accounts associated with roster members. Exploitation requires the vulnerable plugin to be installed and its affected AJAX action to be reachable.

mitigation

Upgrade WP Roster to version 2.35 or later. Restrict public access to the affected site until the update is applied.

fixed in 2.35

check
no
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.
–
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
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-28 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-28 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2840",
  "cve_id": "CVE-2026-115255",
  "display_id": "CVE-2026-115255",
  "ghsa_id": "GHSA-j835-2vx3-j669",
  "euvd_id": "EUVD-2026-111731",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated account deletion in WP Roster",
  "summary": "WP Roster versions before 2.35 are affected by missing authorization and nonce validation in an AJAX action. An unauthenticated attacker can delete WordPress user accounts associated with roster members. Exploitation requires the vulnerable plugin to be installed and its affected AJAX action to be reachable.",
  "mitigation": "Upgrade WP Roster to version 2.35 or later. Restrict public access to the affected site until the update is applied.",
  "vendor": null,
  "product": "WP Roster",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.35"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.35"
      ],
      "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": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.37847365,
  "t0_at": "2026-10-28T06:00:27.222000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T06:00:27.222000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T06:00:27.222000+00:00",
      "url": "https://github.com/advisories/GHSA-j835-2vx3-j669"
    }
  }
}

published 2026-10-28 07:33Z
last change 2026-10-28 10:05Z

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.