CVE-2026-106013: Jupiter X Core authentication bypass vulnerability

critical 9.8 published 2026-10-28 · updated 2026-10-29

Affected versions: 4.61.0 and older
Fixed in: 4.62.0 *
Latest version: 4.62.0
Severity: Critical · CVSS 9.8
Active installs: 70,000+
Type: Authentication bypass

* The source does not name a fixed version; this is the first wordpress.org release after the last affected version.

What an attacker needs

Access: None. No account or login is needed.

CVSS vector (score by Wordfence): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do now

Update Jupiter X Core to 4.62.0 or newer: Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
Not sure which version you run? Check your version against every known Jupiter X Core issue. With WP-CLI: wp plugin get jupiterx-core --field=version.
If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

The advisory

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.

Description from the CVE record, published by Wordfence (the CVE Numbering Authority), via the NVD entry for CVE-2026-106013.

References

NVD CVE-2026-106013 nvd.nist.gov
Wordfence advisory www.wordfence.com
Code change (fix) plugins.trac.wordpress.org

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Where this data comes from

CVE record, score and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Versions and install counts: wordpress.org/plugins/jupiterx-core (Plugins API), fetched 2026-11-04.
The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.