CVE-2026-110963

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

GHSA-78p4-p67c-wwv7 ↗EUVD-2026-119478 ↗

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.
Userplace <= 1.2.0
ETK-2026-3882Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 28msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h19m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Userplace WordPress plugin versions through 1.2.0 expose an AJAX operation without adequate authorization controls. An unauthenticated attacker who can reach the affected site may create an administrator account or alter site options, potentially taking control of the site.

mitigation

Disable the Userplace plugin until the maintainer provides a corrected release. Restrict public access to the affected WordPress site or its AJAX endpoint where operationally feasible.

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.
contextual
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
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3882",
  "cve_id": "CVE-2026-110963",
  "display_id": "CVE-2026-110963",
  "ghsa_id": "GHSA-78p4-p67c-wwv7",
  "euvd_id": "EUVD-2026-119478",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated AJAX authorization bypass in Userplace",
  "summary": "Userplace WordPress plugin versions through 1.2.0 expose an AJAX operation without adequate authorization controls. An unauthenticated attacker who can reach the affected site may create an administrator account or alter site options, potentially taking control of the site.",
  "mitigation": "Disable the Userplace plugin until the maintainer provides a corrected release. Restrict public access to the affected WordPress site or its AJAX endpoint where operationally feasible.",
  "vendor": null,
  "product": "Userplace",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Userplace",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.84790115,
  "t0_at": "2026-11-08T06:00:31.251000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T06:00:31.251000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T06:00:31.251000+00:00",
      "url": "https://github.com/advisories/GHSA-78p4-p67c-wwv7"
    }
  }
}

published 2026-11-08 07:00Z
last change 2026-11-08 07:19Z

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.