CVE-2026-94538

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

EUVD-2026-96217 ↗

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.
JoomUnited WP File Download <= 6.3.9
CWE-862 Missing Authorization
ETK-2026-1151Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 18h 16msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+27h52m
0
+2h
+4h
+6h
+8h
+10h

description

WP File Download versions through 6.3.9 do not adequately enforce permissions for certain file-management actions. An authenticated user with subscriber-level access or higher may alter file publication and category state, remove managed files, or clear the plugin’s trash.

mitigation

Restrict untrusted users from obtaining subscriber or higher accounts, or disable the plugin where that restriction is not feasible. Apply a vendor release that explicitly fixes this issue when one is available.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%15th percentile
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 06: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.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-10 06:40Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1151",
  "cve_id": "CVE-2026-94538",
  "display_id": "CVE-2026-94538",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-96217",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in WP File Download",
  "summary": "WP File Download versions through 6.3.9 do not adequately enforce permissions for certain file-management actions. An authenticated user with subscriber-level access or higher may alter file publication and category state, remove managed files, or clear the plugin’s trash.",
  "mitigation": "Restrict untrusted users from obtaining subscriber or higher accounts, or disable the plugin where that restriction is not feasible. Apply a vendor release that explicitly fixes this issue when one is available.",
  "vendor": "JoomUnited",
  "product": "WP File Download",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 6.3.9"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WP File Download",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": 0.0025,
  "epss_percentile": 0.1514,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.35215783333334,
  "t0_at": "2026-10-10T06:40:12.227000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T06:40:12.227000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T06:40:12.227000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94538"
    }
  }
}

published 2026-10-10 09:35Z
last change 2026-10-21 04:45Z

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.