Quick answers
- Is CVE-2026-19652 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19652 being exploited in the wild.
- How severe is CVE-2026-19652?
- Critical severity, with a CVSS score of 9.8, published 2 October 2026.
- Which products and versions are affected?
- Divi Engine Divi Membership up to and including 2.2.0.
- Is there a fix for CVE-2026-19652?
- Yes: fixed in 3.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19652 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19652?
- Check whether you run Divi Engine Divi Membership at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.0.0
Technical details
The `dmem_form_submit_handler()` function in the registration handler determines a new user's role by iterating through all WordPress roles and calling `password_verify()` against an attacker-supplied bcrypt hash in the `form_id` POST parameter, without role validation or whitelisting. An attacker can submit a pre-computed bcrypt hash of the string "administrator" to match the hashed administrator role, then submit `auto_login=on` to be immediately logged in as administrator. While the exploit requires a WordPress nonce, this nonce is publicly visible on any page with the registration form.
Affected products
- Divi Engine Divi Membership up to and including 2.2.0
Timeline
- 2026-10-02: disclosed