CVE-2026-75927

validatedZero produced an exploit or a check.

GHSA-pv68-4cpj-v6j3 ↗EUVD-2026-74758 ↗

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.+34d
publishpress User Role Editor – PublishPress Capabilities: Access Control and User Roles <= 2.50.0
ETK-2026-1901Zero's internal tracking ID, independent of the CVE number., permanent identifier
+38dTTV
34mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−34dtrigger signal +0dkev+1.0dcheck available+4.8dagent stopped
−30d
−20d
−10d

description

PublishPress Capabilities versions through 2.50.0 can assign elevated plugin management permissions to the WordPress Editor role after activation. An authenticated Editor can then alter non-administrator roles and plugin settings; administrator-level access is not established by the evidence.

mitigation

Until a corrected release is available, disable the plugin on affected sites or remove its management permissions from the Editor role. Review Editor assignments, role permissions, and relevant plugin settings for unauthorized changes.

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.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.64%49th percentile
agent run time
34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-09 07:40Z
Δ 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.
+34d

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-09-09 07:40Z
  2. 2026-10-13
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-13 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1901",
  "cve_id": "CVE-2026-75927",
  "display_id": "CVE-2026-75927",
  "ghsa_id": "GHSA-pv68-4cpj-v6j3",
  "euvd_id": "EUVD-2026-74758",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Privilege escalation in PublishPress Capabilities",
  "summary": "PublishPress Capabilities versions through 2.50.0 can assign elevated plugin management permissions to the WordPress Editor role after activation. An authenticated Editor can then alter non-administrator roles and plugin settings; administrator-level access is not established by the evidence.",
  "mitigation": "Until a corrected release is available, disable the plugin on affected sites or remove its management permissions from the Editor role. Review Editor assignments, role permissions, and relevant plugin settings for unauthorized changes.",
  "vendor": "publishpress",
  "product": "User Role Editor – PublishPress Capabilities: Access Control and User Roles",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.50.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "User Role Editor – PublishPress Capabilities: Access Control and User Roles",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0064,
  "epss_percentile": 0.4969,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 33.71041351666667,
  "t0_at": "2026-09-09T07:40:56.043000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-17T19:23:52.020030+00:00",
      "days": 38.48814788229166,
      "is_lower_bound": false,
      "measured_at": "2026-09-09T07:40:56.043000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-13T00:00:00+00:00",
      "days": 34,
      "is_lower_bound": false,
      "measured_at": "2026-09-09T07:40:56.043000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-75927"
    },
    "trigger_signal": {
      "at": "2026-10-13T00:00:00+00:00",
      "days": 33.67990690972222,
      "is_lower_bound": false,
      "measured_at": "2026-09-09T07:40:56.043000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-75927"
    }
  }
}

published 2026-10-17 18:50Z
last change 2026-10-21 18:49Z

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.