CVE-2026-83526

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

GHSA-p776-3xx4-5fcg ↗EUVD-2026-96092 ↗

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.
foliovision FV Player 8 <= 8.1.7
ETK-2026-1150Zero's internal tracking ID, independent of the CVE number., permanent identifier
10d 19h 13msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h05m
0
+2h
+6h
+8h
+10h
+12h

description

FV Player 8 for WordPress versions 8.1.7 and earlier are affected by an arbitrary file upload flaw. An authenticated subscriber-level or higher account may upload a potentially executable file and could achieve code execution if it can satisfy a race-condition requirement.

mitigation

Update FV Player 8 to a vendor-confirmed release newer than 8.1.7. Until then, deactivate the plugin or prevent untrusted subscriber and higher-privilege accounts from accessing the site.

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.64%49th percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 05:30Z
Δ 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 05:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-10 05:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1150",
  "cve_id": "CVE-2026-83526",
  "display_id": "CVE-2026-83526",
  "ghsa_id": "GHSA-p776-3xx4-5fcg",
  "euvd_id": "EUVD-2026-96092",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file upload in FV Player 8",
  "summary": "FV Player 8 for WordPress versions 8.1.7 and earlier are affected by an arbitrary file upload flaw. An authenticated subscriber-level or higher account may upload a potentially executable file and could achieve code execution if it can satisfy a race-condition requirement.",
  "mitigation": "Update FV Player 8 to a vendor-confirmed release newer than 8.1.7. Until then, deactivate the plugin or prevent untrusted subscriber and higher-privilege accounts from accessing the site.",
  "vendor": "foliovision",
  "product": "FV Player 8",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 8.1.7"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FV Player 8",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0064,
  "epss_percentile": 0.4998,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.83017,
  "t0_at": "2026-10-10T05:30:58.064000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T05:30:58.064000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T05:30:58.064000+00:00",
      "url": "https://github.com/advisories/GHSA-p776-3xx4-5fcg"
    }
  }
}

published 2026-10-10 09:06Z
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.