CVE-2026-119259

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

GHSA-32wc-jrqc-fp7p ↗EUVD-2026-117903 ↗

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.
All-in-One Video Gallery < 5.1.0
fixed in 5.1.0
ETK-2026-3699Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 08msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h23m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

All-in-One Video Gallery versions before 5.1.0 allow unauthenticated visitors to modify view-count and duration metadata on arbitrary WordPress posts. This can affect published, private, and draft posts when the plugin is installed and reachable by an attacker.

mitigation

Upgrade All-in-One Video Gallery to version 5.1.0 or later. Until the update is applied, restrict unauthenticated access to the affected plugin functionality where possible.

fixed in 5.1.0

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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3699",
  "cve_id": "CVE-2026-119259",
  "display_id": "CVE-2026-119259",
  "ghsa_id": "GHSA-32wc-jrqc-fp7p",
  "euvd_id": "EUVD-2026-117903",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthorized post metadata modification in All-in-One Video Gallery",
  "summary": "All-in-One Video Gallery versions before 5.1.0 allow unauthenticated visitors to modify view-count and duration metadata on arbitrary WordPress posts. This can affect published, private, and draft posts when the plugin is installed and reachable by an attacker.",
  "mitigation": "Upgrade All-in-One Video Gallery to version 5.1.0 or later. Until the update is applied, restrict unauthenticated access to the affected plugin functionality where possible.",
  "vendor": null,
  "product": "All-in-One Video Gallery",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.1.0"
      ],
      "package_name": "All-in-One Video Gallery",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.37945416666667,
  "t0_at": "2026-11-06T06:00:26.207000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T06:00:26.207000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T06:00:26.207000+00:00",
      "url": "https://github.com/advisories/GHSA-32wc-jrqc-fp7p"
    }
  }
}

published 2026-11-06 06:50Z
last change 2026-11-06 08:12Z

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.