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.

Project Subscriptions

Vendors Products
Artbees Subscribe
Jupiter X Core Subscribe
Wordpress-extensions Subscribe
Jupiter X Core Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Mon, 16 Nov 2026 10:45:00 +0000

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

Thu, 29 Oct 2026 02:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Wed, 28 Oct 2026 01:45:00 +0000

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'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-29T01:52:00.079Z

Reserved: 2026-10-06T12:15:24.328Z

Link: CVE-2026-106013

cve-icon Vulnrichment

Updated: 2026-10-29T01:42:38.365Z

cve-icon NVD

Status : Deferred

Published: 2026-10-28T02:17:01.303

Modified: 2026-10-29T02:16:46.157

Link: CVE-2026-106013

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-16T10:06:47Z

Weaknesses