CVE-2026-19660: Divi Membership (WordPress plugin) · Improper Authentication
Affects Divi Membership (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DiviEngineDivi Membership | Affected
| Fixed in– |
AI-suggested
Until a fix is available, disabling or removing the Divi Membership plugin or restricting access to the vulnerable endpoint may reduce exposure.
Description
Divi Membership plugin for WordPress versions up to 2.3.0 contains an authentication bypass vulnerability. The vulnerability arises from the process_paypal_callback function accepting a base64-encoded paypal_param GET parameter without proper validation or verification. This allows unauthenticated attackers to impersonate any WordPress user, including administrators, by supplying an arbitrary user ID. The vulnerability leads to full site takeover. The PayPal gateway class is always instantiated, making the vulnerable code active on every front-end request.