CVE-2026-85568

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

GHSA-f222-q2vh-g6q6 ↗EUVD-2026-91938 ↗

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 >= 1.5.139, < 2.0.21
fixed in 2.0.21
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-599, permanent identifier
16d 06h 06msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+41h37m
0
+2h
+4h
+6h
+8h
+10h

description

Unlimited Elements for Elementor versions before 2.0.21 are affected by an SQL injection flaw. An unauthenticated attacker may retrieve non-public content when the related widget option is configured away from its default setting.

mitigation

Update Unlimited Elements for Elementor to version 2.0.21 or later. Until the update is applied, keep the related widget option at its default setting to reduce exposure.

fixed in 2.0.21

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-599",
  "cve_id": "CVE-2026-85568",
  "display_id": "CVE-2026-85568",
  "ghsa_id": "GHSA-f222-q2vh-g6q6",
  "euvd_id": "EUVD-2026-91938",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in Unlimited Elements for Elementor",
  "summary": "Unlimited Elements for Elementor versions before 2.0.21 are affected by an SQL injection flaw. An unauthenticated attacker may retrieve non-public content when the related widget option is configured away from its default setting.",
  "mitigation": "Update Unlimited Elements for Elementor to version 2.0.21 or later. Until the update is applied, keep the related widget option at its default setting to reduce exposure.",
  "vendor": null,
  "product": "Unlimited Elements for Elementor",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.5.139, < 2.0.21"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.21"
      ],
      "package_name": "Unlimited Elements for Elementor",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 6.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": 0.0022,
  "epss_percentile": 0.114,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.45358395,
  "t0_at": "2026-10-03T06:00:25.854000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-03T06:00:25.854000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T06:00:25.854000+00:00",
      "url": "https://github.com/advisories/GHSA-f222-q2vh-g6q6"
    }
  }
}

published 2026-10-04 23:00Z
last change 2026-10-21 05:00Z

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.