CVE-2026-106013
CriticalCVSS 9.8Summary
The Jupiter X Core plugin for WordPress (up to and including 4.61.0) is vulnerable to authentication bypass in its Twitter/X social login handler. The verify_twitter_callback function fails to reassign the returned credentials to the TwitterOAuth client, so the subsequent API call remains signed with the site operator's stored token, and the plugin authenticates a WordPress account based solely on the X app owner's email address.
Risk Assessment
An unauthenticated attacker can gain authenticated access as the WordPress user whose email matches the X app owner, typically the site administrator, leading to full site compromise.
Recommendation
Update Jupiter X Core to a version later than 4.61.0 or temporarily disable Twitter/X login; review administrative accounts and sessions for unauthorized access.
Other vulnerabilities in Jupiter X Core
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS