CVE-2026-95534

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

GHSA-5v8m-ppqr-qj2h ↗EUVD-2026-94488 ↗

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.
Unlimited Elements For Elementor (Free Widgets, Addons, Templates) >= n/a, <= 2.0.19
ETK-2026-915, permanent identifier
13d 21h 02msince last run
42mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+6h43m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Unlimited Elements For Elementor versions through 2.0.19 are affected by an insecure deserialization flaw. An attacker with the required privileges may be able to trigger object injection through the affected plugin.

mitigation

Update the plugin to a vendor release newer than 2.0.19 after confirming it includes the correction. Until then, deactivate the plugin where feasible and restrict access to accounts permitted to administer or use it.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%20th percentile
agent run time
42m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 17: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: 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-07 17:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-07 17:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-915",
  "cve_id": "CVE-2026-95534",
  "display_id": "CVE-2026-95534",
  "ghsa_id": "GHSA-5v8m-ppqr-qj2h",
  "euvd_id": "EUVD-2026-94488",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Object injection in Unlimited Elements for Elementor",
  "summary": "Unlimited Elements For Elementor versions through 2.0.19 are affected by an insecure deserialization flaw. An attacker with the required privileges may be able to trigger object injection through the affected plugin.",
  "mitigation": "Update the plugin to a vendor release newer than 2.0.19 after confirming it includes the correction. Until then, deactivate the plugin where feasible and restrict access to accounts permitted to administer or use it.",
  "vendor": "Unlimited Elements",
  "product": "Unlimited Elements For Elementor (Free Widgets, Addons, Templates)",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 2.0.19"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "unlimited-elements-for-elementor",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0029,
  "epss_percentile": 0.2016,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 41.9449727,
  "t0_at": "2026-10-07T17:00:23.166000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T17:00:23.166000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T17:00:23.166000+00:00",
      "url": "https://github.com/advisories/GHSA-5v8m-ppqr-qj2h"
    }
  }
}

published 2026-10-07 23:01Z
last change 2026-10-21 19:57Z

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.