WP Security CheckVulnerability data as of October 28, 2026

Vulnerability alerts / October 27, 2026

Vulnerability in Jupiter X Core — CVE-2026-106013

CriticalSeverity
CVSS 9.8
—Estimated exploit probability
EPSS
70,000+ sitesInstalls
4.62.0Fixed in

What to do now

Update Jupiter X Core to 4.62.0 or later.

Affected versions

  • Everything up to and including 4.61.0

Affected: Jupiter X Core (plugin, jupiterx-core)

Check: The plugin on wordpress.org / Our record for Jupiter X Core

What the vulnerability is

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.

This description is reproduced verbatim from the public vulnerability record.

Sources

Part of this record comes from Wordfence Intelligence. Original: https://www.wordfence.com/threat-intel/vulnerabilities/id/1ad42de2-9ed1-4cf6-a031-22789be4cbe2
Copyright 2012-2026 Defiant Inc. / Full license text

This page is compiled automatically from public databases. Accuracy is not guaranteed; confirm against the vendor advisory before acting.

See other alerts