Technical impact
The Jupiter X Core WordPress plugin allows an unauthenticated attacker to bypass the login process when using the Twitter/X social login feature. The flaw occurs in the callback handler after a user's oauth_verifier is exchanged for an access token. The handler fails to reassign the returned credentials to the TwitterOAuth client, so the verification request is signed with the site's stored credentials. Consequently, the Twitter API returns the profile of the X application owner, and the plugin logs the attacker in as the WordPress user whose email matches that owner—typically the site administrator. This results in full administrative access to the site without authentication credentials, violating confidentiality, integrity, and availability. The vulnerability is present in all plugin versions up to and including 4.61.0 and is triggered by an unauthenticated user interacting with the Twitter/X social login button. Because the flaw relies exclusively on the exposed social login flow and requires no privileged information, the potential impact is high, and exploitation is highly probable for sites that have enabled Twitter/X login. The CVSS score of 9.8 reflects the critical nature of the issue, although the EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog.
Affected Systems
WordPress sites that have installed the artbees Jupiter X Core plugin version 4.61.0 or earlier and have enabled the Twitter/X social login feature. Vendors: artbees. Products: Jupiter X Core. Affected versions: any release up to and including 4.61.0.
Risk and Exploitability
The attack vector is an unauthenticated user clicking the Twitter/X social login button, which subsequently triggers the vulnerability. Once the attacker is authenticated as the site administrator, they can execute any administrative action via the WordPress dashboard. Exploitation requires no additional credentials, and no complex network configuration. The high CVSS score of 9.8 indicates a severe risk, and the lack of a KEV listing does not diminish the likelihood of exploitation for sites that enable the vulnerable feature.