CVE-2026-115252

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

GHSA-6ch9-px9g-8jxj ↗EUVD-2026-119932 ↗

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.
Confection WordPress Cable >= 0.4.0, <= 0.4.7
ETK-2026-3946Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 19h 44msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h51m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Confection WordPress Cable versions 0.4.0 through 0.4.7 are affected by an unprotected settings update path. An unauthenticated attacker may modify a setting in a way that leads to PHP execution on the WordPress server when the affected plugin is installed and reachable.

mitigation

Deactivate and remove Confection WordPress Cable 0.4.0 through 0.4.7 until the maintainer publishes a corrected release. Restrict public access to the affected WordPress site or its administrative endpoints if the plugin cannot be removed immediately.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 10:24Z
Δ 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-09 10:24Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3946",
  "cve_id": "CVE-2026-115252",
  "display_id": "CVE-2026-115252",
  "ghsa_id": "GHSA-6ch9-px9g-8jxj",
  "euvd_id": "EUVD-2026-119932",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated PHP code injection in Confection WordPress Cable",
  "summary": "Confection WordPress Cable versions 0.4.0 through 0.4.7 are affected by an unprotected settings update path. An unauthenticated attacker may modify a setting in a way that leads to PHP execution on the WordPress server when the affected plugin is installed and reachable.",
  "mitigation": "Deactivate and remove Confection WordPress Cable 0.4.0 through 0.4.7 until the maintainer publishes a corrected release. Restrict public access to the affected WordPress site or its administrative endpoints if the plugin cannot be removed immediately.",
  "vendor": null,
  "product": "Confection WordPress Cable",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.0, <= 0.4.7"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Confection WordPress Cable",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.41043335,
  "t0_at": "2026-11-09T10:24:50.507000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T10:24:50.507000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T10:24:50.507000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115252"
    }
  }
}

published 2026-11-09 10:55Z
last change 2026-11-11 06:34Z

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.