CVE-2026-126119

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

GHSA-qr6f-qp3w-9j3f ↗EUVD-2026-124854 ↗

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.
Streamit < 1.3.10
fixed in 1.3.10
ETK-2026-4353Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 04msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h55m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Streamit versions before 1.3.10 expose an AJAX route that lacks authorization and request-verification controls. An unauthenticated remote attacker who can reach that route may invoke PHP functions, enabling account privilege changes and potentially code execution.

mitigation

Upgrade the Streamit WordPress plugin to version 1.3.10 or later. Restrict public access to the affected WordPress site until the update is applied.

fixed in 1.3.10

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-13 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4353",
  "cve_id": "CVE-2026-126119",
  "display_id": "CVE-2026-126119",
  "ghsa_id": "GHSA-qr6f-qp3w-9j3f",
  "euvd_id": "EUVD-2026-124854",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated function invocation in Streamit",
  "summary": "Streamit versions before 1.3.10 expose an AJAX route that lacks authorization and request-verification controls. An unauthenticated remote attacker who can reach that route may invoke PHP functions, enabling account privilege changes and potentially code execution.",
  "mitigation": "Upgrade the Streamit WordPress plugin to version 1.3.10 or later. Restrict public access to the affected WordPress site until the update is applied.",
  "vendor": null,
  "product": "Streamit",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.3.10"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.3.10"
      ],
      "package_name": "Streamit",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 23.665521883333334,
  "t0_at": "2026-11-13T06:00:09.870000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T06:00:09.870000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T06:00:09.870000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126119"
    }
  }
}

published 2026-11-13 06:31Z
last change 2026-11-13 07:43Z

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.