Cyber & AI intelligence
Wasteland.
Briefs indexed3305
Issues34
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-106013 2026-10-28

Jupiter X Core WordPress Plugin Auth Bypass Lets Attackers Log In as the X App Owner (CVE-2026-106013)

"A critical authentication bypass (CVSS 9.8) in the Twitter/X Social Login handler of the Jupiter X Core WordPress plugin lets unauthenticated attackers log in as the WordPress user whose email matches the site's X…"

A critical authentication bypass (CVSS 9.8) in the Twitter/X Social Login handler of the Jupiter X Core WordPress plugin lets unauthenticated attackers log in as the WordPress user whose email matches the site's X application owner, who is typically the site administrator.

What Is It

CVE-2026-106013 is an authentication bypass (CWE-287) in the verify_twitter_callback function of Jupiter X Core by artbees. When a visitor signs in with X, the handler exchanges the visitor's oauth_verifier for an access token. It never calls setOauthToken() to load those returned credentials into the TwitterOAuth client.

Because of that, the next account/verify_credentials API call is still signed with the site operator's stored Access Token and Access Token Secret, not the visitor's token. The X API returns the profile of the X application owner instead of the visitor. The plugin then finds a WordPress account using only that owner's email address and authenticates it with wp_set_auth_cookie().

Why It Matters

What's Vulnerable

Vendor Product Affected Versions
artbees Jupiter X Core (WordPress plugin) All versions up to and including 4.61.0

The vulnerable code path is the Twitter/X Social Login handler in the plugin's Raven forms module. NVD lists no CPEs for this record. The NVD status is "Deferred." The CVE was published 2026-10-28.

Patch Status

The supplied data does not name a fixed version. The references include a WordPress plugin repository changeset (3759312) to the Twitter social login handler (twitter.php), which points to a code fix in the plugin trunk. No CISA KEV required action or due date applies, because the CVE has no KEV entry.

Recommended steps for site owners running Jupiter X Core 4.61.0 or earlier:

Sources