CVE-2026-19652

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

GHSA-f7mc-wpjj-g5hj ↗EUVD-2026-91635 ↗

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.
DiviEngine Divi Membership <= 2.2.0
CWE-269 Improper Privilege Management
ETK-2026-339, permanent identifier
17d 18h 56msince last run
34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+27h21m
0
+2h
+4h
+6h
+8h
+10h

description

Divi Membership for WordPress through version 2.2.0 is affected by an account-registration privilege escalation flaw. An unauthenticated visitor can create an administrator-level account if a Divi Membership registration form is publicly reachable.

mitigation

Disable or remove Divi Membership registration forms and restrict public access to affected sites until a vendor update is available. Review administrator accounts and revoke any unexpected accounts.

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.33%25th percentile
agent run time
34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 13:29Z
Δ 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-02 13:29Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-339",
  "cve_id": "CVE-2026-19652",
  "display_id": "CVE-2026-19652",
  "ghsa_id": "GHSA-f7mc-wpjj-g5hj",
  "euvd_id": "EUVD-2026-91635",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated privilege escalation in Divi Membership",
  "summary": "Divi Membership for WordPress through version 2.2.0 is affected by an account-registration privilege escalation flaw. An unauthenticated visitor can create an administrator-level account if a Divi Membership registration form is publicly reachable.",
  "mitigation": "Disable or remove Divi Membership registration forms and restrict public access to affected sites until a vendor update is available. Review administrator accounts and revoke any unexpected accounts.",
  "vendor": "DiviEngine",
  "product": "Divi Membership",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Divi Membership",
      "purl": null
    }
  ],
  "cwes": [
    269
  ],
  "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.2507,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.29313905,
  "t0_at": "2026-10-02T13:29:05.573000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T13:29:05.573000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T13:29:05.573000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-19652"
    }
  }
}

published 2026-10-02 13:43Z
last change 2026-10-21 05:31Z

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.