CVE-2026-66568

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

GHSA-7hr6-wjj3-8fvf ↗EUVD-2026-96522 ↗

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

description

axiomthemes Original versions 1.9.0 and earlier are affected by a PHP object injection flaw. An unauthenticated attacker may be able to trigger unsafe object handling without needing an account.

mitigation

Restrict access to affected installations to trusted users and networks until a corrected vendor release is available. Upgrade to a vendor-provided fixed version when one is published.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
20m
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

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 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-66568

{
  "etk_id": "ETK-2026-1196",
  "cve_id": "CVE-2026-66568",
  "display_id": "CVE-2026-66568",
  "ghsa_id": "GHSA-7hr6-wjj3-8fvf",
  "euvd_id": "EUVD-2026-96522",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated PHP object injection in axiomthemes Original",
  "summary": "axiomthemes Original versions 1.9.0 and earlier are affected by a PHP object injection flaw. An unauthenticated attacker may be able to trigger unsafe object handling without needing an account.",
  "mitigation": "Restrict access to affected installations to trusted users and networks until a corrected vendor release is available. Upgrade to a vendor-provided fixed version when one is published.",
  "vendor": "axiomthemes",
  "product": "Original",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 1.9.0"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Original",
      "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.0031,
  "epss_percentile": 0.2283,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.493753916666666,
  "t0_at": "2026-10-10T19:36:13.592000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T19:36:13.592000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:36:13.592000+00:00",
      "url": "https://github.com/advisories/GHSA-7hr6-wjj3-8fvf"
    }
  }
}

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