CVE-2026-106013

Jupiter X Core <= 4.61.0 - Unauthenticated Authentication Bypass via Twitter/X Social Login oauth_verifier Parameter

Published Oct 28, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor‑supplied fix or upgrade to the latest Jupiter X Core version (≥ 4.61.1).
  • If an upgrade cannot be performed immediately, disable the Twitter/X social login option in the plugin settings to block the vulnerable entry point.
  • As a temporary safeguard, monitor WordPress user accounts for abnormal login activity and consider restricting the administrative email address or changing the admin password promptly.

Generated by OpenCVE AI on October 28, 2026 at 02:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Artbees
Artbees jupiter X Core
Wordpress-extensions
Wordpress-extensions jupiter X Core
Vendors & Products Artbees
Artbees jupiter X Core
Wordpress-extensions
Wordpress-extensions jupiter X Core
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Jupiter X Core <= 4.61.0 - Unauthenticated Authentication Bypass via Twitter/X Social Login oauth_verifier Parameter
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Oct 29, 2026, 1:52 AM
Reserved
Oct 6, 2026, 12:15 PM
Status
Deferred
Published
Oct 28, 2026, 2:17 AM
Modified
Oct 29, 2026, 2:16 AM