Jupiter X Core auth bypass in Twitter/X Social Login
artbees Jupiter X Core
artbees Jupiter X Core
| Product | Affected | Fixed in |
|---|---|---|
| artbees Jupiter X Core |
| No fix yet |
The Jupiter X Core plugin for WordPress is vulnerable to Authentication Bypass via the Twitter/X Social Login handler in all versions up to and including 4.61.0. The vulnerability exists within the verify_twitter_callback function because after exchanging the visitor's oauth_verifier for their access token, the handler never calls setOauthToken() to reassign the returned credentials to the TwitterOAuth client, causing the subsequent account/verify_credentials API call to remain signed with the site operator's stored Access Token and Access Token Secret rather than the authenticating visitor's token. This causes the X API to return the profile of the X application owner instead of the signing-in visitor, and the plugin then resolves and authenticates a WordPress account solely by matching that owner's email address via wp_set_auth_cookie(), allowing unauthenticated attackers to gain authenticated access as the WordPress user whose email corresponds to the X app owner, who is typically the site administrator.
From the CVE record · Wordfence
Jupiter X Core for WordPress is vulnerable to authentication bypass in its Twitter/X Social Login handler. An unauthenticated attacker can sign in as the WordPress user whose email matches the X application owner's email, typically the site administrator, because the handler uses the site operator's credentials when verifying the X profile.
Anyone running artbees Jupiter X Core for WordPress version 4.61.0 or earlier should check their installation.