CVE-2026-97331

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

GHSA-m2gh-g9gw-hjhf ↗EUVD-2026-94191 ↗

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.
User Private Files < 2.1.9
fixed in 2.1.9
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-1307Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 00h 13msince last run
53mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+119h29m
0
+2h
+4h
+6h
+8h
+10h

description

User Private Files versions before 2.1.9 for WordPress do not verify that a requested user is associated with a document before returning an email address. An authenticated low-privilege user may obtain email addresses for registered accounts, including administrators.

mitigation

Upgrade User Private Files to version 2.1.9 or later. Restrict access to authenticated accounts until the update is applied.

fixed in 2.1.9

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.18%6th percentile
agent run time
53m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 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: 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-07 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1307",
  "cve_id": "CVE-2026-97331",
  "display_id": "CVE-2026-97331",
  "ghsa_id": "GHSA-m2gh-g9gw-hjhf",
  "euvd_id": "EUVD-2026-94191",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization flaw exposes user emails in User Private Files",
  "summary": "User Private Files versions before 2.1.9 for WordPress do not verify that a requested user is associated with a document before returning an email address. An authenticated low-privilege user may obtain email addresses for registered accounts, including administrators.",
  "mitigation": "Upgrade User Private Files to version 2.1.9 or later. Restrict access to authenticated accounts until the update is applied.",
  "vendor": null,
  "product": "User Private Files",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.1.9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.1.9"
      ],
      "package_name": "User Private Files",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 4.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
  "epss_score": 0.0018,
  "epss_percentile": 0.0676,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 53.39231626666667,
  "t0_at": "2026-10-07T06:00:08.993000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T06:00:08.993000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T06:00:08.993000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97331"
    }
  }
}

published 2026-10-12 04:17Z
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.