Quick answers
- Is CVE-2026-19660 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19660 being exploited in the wild.
- How severe is CVE-2026-19660?
- 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.3.0.
- Is there a fix for CVE-2026-19660?
- 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-19660 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19660?
- 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 `process_paypal_callback` function hooked to the `init` action accepts a base64-encoded `paypal_param` GET parameter with no IPN validation, signature check, ownership verification, or nonce protection. The attacker-controlled user ID is passed directly to `wp_set_current_user()` and `wp_set_auth_cookie()`, granting session access. The PayPal gateway class is instantiated unconditionally on all requests regardless of PayPal configuration, ensuring the vulnerable hook is always active.
Affected products
- Divi Engine Divi Membership up to and including 2.3.0
Timeline
- 2026-10-02: disclosed