# CVE-2026-19652: Divi Membership <= 2.2.0 - Unauthenticated Privilege Escalation via 'form_id' Parameter

> Unauthenticated attackers can escalate privileges to administrator by manipulating the form_id parameter in the Divi Membership plugin, leading to full site takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-f7mc-wpjj-g5hj

## What is CVE-2026-19652?

CVE-2026-19652 is a critical vulnerability in DiviEngine Divi Membership, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Divi Membership plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 2.2.0. This is due to the `dmem_form_submit_handler()` function determining the new user's role by iterating all WordPress roles and calling `password_verify()` against an attacker-controlled bcrypt hash supplied in the `form_id` POST parameter, with no validation or whitelist of allowed roles. This makes it possible for unauthenticated attackers to register a new account with the administrator role by submitting a locally computed bcrypt hash of `administrator` as `form_id`, and when `auto_login=on` is submitted, be immediately authenticated as that administrator in the same request, resulting in full site takeover. Exploitation requires a WordPress nonce, but that nonce is publicly emitted on any page rendering the Divi Membership registration form and is therefore obtainable by any unauthenticated visitor.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-19652?


## How do I fix CVE-2026-19652?

No fix has been published for CVE-2026-19652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19652 being exploited?

There is no known exploitation of CVE-2026-19652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19652 and fix it if it is affected.

What it is: CVE-2026-19652 is a critical vulnerability in DiviEngine Divi Membership, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19652 in the wild and no public exploit code.

Affected product: DiviEngine Divi Membership. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19652/ (Markdown: https://insights.sbomify.com/CVE-2026-19652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19652
- OSV: https://osv.dev/vulnerability/CVE-2026-19652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19652/
Summaries are generated and may contain mistakes; the official description above is the record.