CVE-2026-92885: Qode Membership <= 2.0.6.2 - Authentication Bypass via Social Login

Published Oct 27, 2026
·
Updated

The Qode Membership plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.0.6.2 via the qodemembershipcheckfacebookuser AJAX action. This is due to a typographic error in the Facebook OAuth token verification guard within the qodemembershiploginuserfromsocialnetwork function — the guard condition tests an undefined variable ($checksocialuseqoder instead of $checksocialuser), causing empty() to always return true and rendering the Graph API token verification branch dead code, leaving wpsetauthcookie() reachable with no credential or token validation whatsoever. This makes it possible for unauthenticated attackers to log in as any existing WordPress account — including Administrator-level accounts — by supplying a known or enumerated administrator login name (rather than an email address) in the response[email] parameter, which the fallback path in getuserby('login', $email) resolves to the matching account. Exploitation does require harvesting a valid qodevalidatefacebooklogin nonce, but this nonce is rendered on any public front-end page containing the [qodeuserlogin] or [qodeuserregister] shortcode and is therefore obtainable without any prior authentication.

Affected Software

1 affected component
Qode Qode Membership<=2.0.6.2

Event History

Oct 27, 2026
CVE Published
via MITRE·08:28 AM
Data Sourced
via MITRE·08:28 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which sites are practically exposed to exploitation?

Sites using an affected version are exposed when a public front-end page renders the [qode_user_login] shortcode or the relevant login form, because that page provides a valid qode_validate_facebook_login nonce required for the AJAX request.

2

What does an attacker need to successfully take over an account?

The attacker needs a valid qode_validate_facebook_login nonce and the login name of an existing WordPress account. No Facebook OAuth token, password, or other credential validation is required by the vulnerable path.

3

How severe can a successful compromise be?

An unauthenticated attacker can authenticate as any existing WordPress account whose login name is known or enumerated. This includes Administrator-level accounts, allowing full site takeover.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203