CVE-2026-19660 DiviEngine CVE debrief

Who should care

WordPress administrators and users of the Divi Membership plugin should assess their exposure and take immediate action to prevent exploitation, considering the potential impact on operators, platforms, vulnerability management, and security teams to ensure comprehensive mitigation and response.

Why it matters

The Divi Membership plugin for WordPress is vulnerable to Authentication Bypass, allowing unauthenticated attackers to log in as any existing WordPress user, including administrators, and potentially leading to full site takeover. WordPress administrators and users of the Divi Membership plugin should assess their exposure and take immediate action to prevent exploitation.

• Full site takeover by unauthenticated attackers
• Ability to log in as any existing WordPress user, including administrators
• Potential for malicious activity, such as data tampering or unauthorized access

Technical summary

The Divi Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 2.3.0. The `process_paypal_callback` function, hooked to the `init` action, accepts a base64-encoded `paypal_param` GET parameter with no IPN validation, no cryptographic signature check, no ownership verification, and no nonce, allowing it to trust an entirely attacker-controlled user ID value that is passed directly to `wp_set_current_user()` and `wp_set_auth_cookie()`.

Defensive priority

High priority for remediation due to critical CVSS score of 9.8 and potential for full site takeover.

Recommended defensive actions

• Immediately update the Divi Membership plugin to a version that fixes the authentication bypass vulnerability
• Verify that the PayPal gateway class is not instantiated unconditionally
• Implement additional security measures to prevent unauthorized access
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the `process_paypal_callback` function, hooked to the `init` action, accepting a base64-encoded `paypal_param` GET parameter with no IPN validation, no cryptographic signature check, no ownership verification, and no nonce.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.