Skip to main content

Divi Membership CVE-2026-19652

| EUVDEUVD-2026-91635 CRITICAL
Improper Privilege Management (CWE-269)
2026-10-02 Wordfence GHSA-f7mc-wpjj-g5hj
9.8
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Load Divi Membership registration page
  2. Delivery
    Harvest public nonce, precompute bcrypt('administrator')
  3. Exploit
    Submit registration with crafted form_id and auto_login=on
  4. Execution
    Role loop matches administrator, account auto-authenticated
  5. Impact
    Full site takeover with admin access

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that a page rendering the Divi Membership registration form be reachable, because the dmem_form_submit_handler() role-selection logic (which calls password_verify() on the attacker-controlled form_id bcrypt hash against every WordPress role with no role whitelist) is the vulnerable path, and the registration form page is where the required WordPress nonce is publicly emitted. The nonce is the only prerequisite and imposes no real limit since any unauthenticated visitor can read it; immediate authentication additionally requires submitting auto_login=on. The practical limiting factors are therefore deployment-specific: the plugin must be installed at version ≤2.2.0 and the registration form must be exposed on a publicly accessible page - there is no authentication, user interaction, or non-default toggle needed beyond that.

Impact

This is a genuine high-priority vulnerability, not an inflated-CVSS artifact. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) is fully consistent with the description: an unauthenticated network attacker can achieve administrator-role registration and immediate authentication in a single request, giving C:H/I:H/A:H and justifying the 9.8 base score. The design flaw is especially dangerous because the sole apparent gate - a WordPress nonce - is publicly emitted on any page rendering the registration form, so it provides no meaningful barrier; this collapses what might look like a configuration-dependent weakness into effectively unauthenticated full takeover wherever the registration form is exposed. Signals are limited, however: no EPSS score was provided, there is no CISA KEV listing, and no public POC is referenced, so exploitation status is 'no public exploit identified at time of analysis' despite the trivial, deterministic nature of the attack. The main limiting factor is deployment - exploitation only works where the Divi Membership registration form is actually rendered and reachable. Given how mechanically simple and reliable the attack is once a vulnerable, exposed site is found, defenders should treat this as urgent for any site running the plugin even though no in-the-wild activity is confirmed in the provided data.

Exploit ScenarioDerived

An unauthenticated attacker loads a WordPress page that renders the Divi Membership registration form, scrapes the publicly emitted nonce, and submits a registration request with the form_id parameter set to a locally computed bcrypt hash of the string 'administrator' plus auto_login=on. The server's role-matching loop verifies the hash against the administrator role, creates the account with admin privileges, and immediately authenticates the attacker in the same request, yielding full site takeover. No public exploit code is identified at time of analysis, but the technique is deterministic and requires only commodity bcrypt tooling.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 02, 2026

Unauthenticated privilege escalation in the Divi Membership plugin for WordPress (versions up to and including 2.2.0) lets any site visitor create a brand-new account with the administrator role and, by also submitting auto_login=on, be logged in as that administrator within the same request - resulting in complete site takeover. The flaw (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) sits in dmem_form_submit_handler(), which derives the new user's role by iterating every WordPress role and calling password_verify() against an attacker-supplied bcrypt hash in the form_id POST parameter, with no whitelist of permitted roles. The only prerequisite is a WordPress nonce, which is publicly emitted on any page that renders the Divi Membership registration form and is therefore readable by any unauthenticated visitor; no public exploit code has been identified at time of analysis.

RemediationAI

No vendor-released patch version is identified in the available intelligence at time of analysis, so the primary action is to deactivate and remove the Divi Membership plugin (or roll back to a pre-registration-handler state is not an option for this branch) until a fixed release appears - monitor the vendor changelog at https://diviengine.com/divi-membership-changelog/ and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/81d46c7a-dfe4-4991-99cc-66e5c6d3e3c8?source=cve for the patched version before reinstalling, and treat any version ≤2.2.0 as vulnerable. If the plugin cannot be removed immediately, eliminate the attack surface by taking every page that renders the Divi Membership registration shortcode or block offline (unpublish, password-protect, or restrict at the web server), since the handler is only exploitable when the nonce-bearing form is reachable; note that the nonce is emitted on any page showing the form, so simply removing the form from navigation while leaving the page published is insufficient. As a compensating control with acknowledged trade-offs, deploy virtual patching at the WAF or reverse-proxy layer to reject POST requests to the plugin's registration/submit endpoint that contain a form_id value shaped like a bcrypt hash (prefixes $2a$, $2b$, $2y$, $2x$) or that pass auto_login=on during registration - this is a stopgap that can cause false positives for legitimate registrations and does not fix the underlying role-assignment logic. Finally, audit wp_users/wp_usermeta for any administrative accounts created since the plugin was installed, remove unauthorized administrators, rotate credentials for all legitimate admin accounts, and review logs for suspicious registrations, since successful exploitation yields immediate authenticated administrator access and full site takeover.

Affected VersionsENISA

Divi Membership 0 ≤2.2.0

Affected Packages

euvd divi_membership no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-269 (Improper Privilege Management): the plugin treats an attacker-controlled credential-like value as an authorization selector. Specifically, dmem_form_submit_handler() loops over all registered WordPress roles and passes each role name as the plaintext argument to password_verify(), with the request-supplied form_id value used as the hash argument. Because password_verify() is designed to compare a plaintext candidate against a stored hash, an attacker who locally computes a bcrypt hash of the string 'administrator' and submits it as form_id will produce a successful verification match for that role, causing the newly registered user to be assigned administrator rights instead of a low-privileged role. There is no allowlist restricting which roles can be assigned and no server-side binding between the hash and a legitimate registration context. When the attacker also submits auto_login=on, the plugin authenticates the new account in the same request, eliminating any need for subsequent login. Exploitation is gated by a WordPress nonce, but that nonce is rendered into any page that outputs the Divi Membership registration form, so it provides no meaningful barrier to an unauthenticated visitor. The affected component is identified by CPE cpe:2.3:a:diviengine:divi_membership:*:*:*:*:*:*:*:* (DiviEngine), with the EUVD record EUVD-2026-91635 listing affected versions as 'Divi Membership 0 ≤2.2.0'; the CVSS vector confirms network reachability with no privileges or user interaction required.

Know when Divi Membership gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Unauthenticated remote request (AV:N/PR:N/UI:N) with a deterministic role bypass (AC:L); gaining admin yields full confidentiality, integrity, and availability impact (C/I/A:H).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Any unauthenticated visitor to a WordPress site running the Divi Membership plugin (versions up to and including 2.2.0) can create a brand-new administrator account and be logged in as that administrator within the same request, resulting in complete takeover of the affected website. Because the plugin is deployed on public-facing membership and marketing sites, this exposes customer records, e-commerce and payment integrations, and the integrity of all published content. With no vendor-released patch identified at time of analysis, leadership should treat every internet-facing site running this plugin as an active, severe exposure and act immediately.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Divi Membership plugin (2.2.0 and earlier) from all internet-facing WordPress sites until a fixed version is available; apply virtual patching at the WAF or edge to block POST requests to the plugin's dmem_form_submit_handler endpoint and requests containing a form_id parameter; disable open registration paths that render the Divi Membership registration form so its publicly emitted nonce is no longer exposed; restrict wp-admin access by IP allowlist or VPN; enable monitoring and alerting for new administrator-role account creation, role changes, and anomalous admin logins; and audit existing administrator accounts for unauthorized additions.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Medium
membership add-on for popular Divi ecosystem, moderate third-party adoption
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy