CVE-2026-66567

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

GHSA-xm2p-xf7g-7qxp ↗EUVD-2026-96521 ↗

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.
AncoraThemes Anesta >= n/a, <= 1.5.3
ETK-2026-1197Zero's internal tracking ID, independent of the CVE number., permanent identifier
10d 04h 06msince last run
56mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+5h05m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Anesta versions 1.5.3 and earlier are affected by an unauthenticated PHP object injection flaw. An unauthenticated remote attacker may be able to inject PHP objects; the available evidence does not identify additional preconditions or resulting impact.

mitigation

Upgrade Anesta to a supported release newer than 1.5.3. Until upgrading, limit public access to affected installations to reduce exposure.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1197",
  "cve_id": "CVE-2026-66567",
  "display_id": "CVE-2026-66567",
  "ghsa_id": "GHSA-xm2p-xf7g-7qxp",
  "euvd_id": "EUVD-2026-96521",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated PHP object injection in Anesta",
  "summary": "Anesta versions 1.5.3 and earlier are affected by an unauthenticated PHP object injection flaw. An unauthenticated remote attacker may be able to inject PHP objects; the available evidence does not identify additional preconditions or resulting impact.",
  "mitigation": "Upgrade Anesta to a supported release newer than 1.5.3. Until upgrading, limit public access to affected installations to reduce exposure.",
  "vendor": "AncoraThemes",
  "product": "Anesta",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 1.5.3"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Anesta",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0033,
  "epss_percentile": 0.2485,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 56.28444498333333,
  "t0_at": "2026-10-10T19:36:12.850000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T19:36:12.850000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:36:12.850000+00:00",
      "url": "https://github.com/advisories/GHSA-xm2p-xf7g-7qxp"
    }
  }
}

published 2026-10-10 23:44Z
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.