Jupiter X Core ≤ 4.61.0: The X Login That Logs Everyone In as the Site Owner (CVE-2026-106013, CVSS 9.8)

Running Jupiter X Core on your site? Check it against CVE-2026-106013 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Jupiter X Core is in the affected range (≤ 4.61.0), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Jupiter X Core ≤ 4.61.0: The X Login That Logs Everyone In as the Site Owner (CVE-2026-106013, CVSS 9.8)

Social login is supposed to answer one question: who is this visitor? In Jupiter X Core's Twitter/X login, the plugin asks that question using the site operator's own credentials — so X always answers with the operator's profile, and the plugin logs the visitor in as that person. The verification step exists. It runs. It just never verifies the visitor.

What Happened

The flaw is tracked as CVE-2026-106013 (CWE-287, improper authentication), with Wordfence as the assigning CNA in the CVE record.

How It Works, Plainly

The bug sits in the verify_twitter_callback function of the plugin's social-login handler:

  1. A visitor starts "Sign in with X." The plugin exchanges the visitor's oauth_verifier for their access token — the step that proves who the visitor is.
  2. It then never calls setOauthToken() to put those returned credentials on the TwitterOAuth client.
  3. The follow-up account/verify_credentials call therefore goes out signed with the site operator's stored Access Token and Access Token Secret — the credentials saved when the site configured its X app.
  4. X quite correctly returns the profile of the person those credentials belong to: the X app owner.
  5. The plugin resolves a WordPress account by matching that owner's email address and calls wp_set_auth_cookie() — logging the visitor in as the account whose email matches the X app owner, who is typically the site administrator.

No password is guessed and no token is stolen. The plugin asks the wrong person "who are you?" and trusts the answer completely.

The Scope, Stated Straight

This path only exists where Jupiter X Core's Twitter/X social login is configured — the site must have set up an X app and enabled that login, because the flaw needs the operator's stored app credentials to abuse. A site running Jupiter X Core without the X social login configured does not expose this handler the same way.

That condition narrows the blast radius; it does not make the flaw minor. Social login is exactly the feature sites enable on their public login and registration pages, and the account on the other end of this one is, typically, an administrator.

Am I Affected?

Check in wp-admin → Plugins: is Jupiter X Core at 4.61.0 or lower, and is its X/Twitter social login set up? Yes to both means act today.

From outside, the plugin's announced version is one of the things our scanner reads: the free mini-scan checks the public readme version for Jupiter X Core (and a dozen other disclosed plugin flaws) and reports a version in the affected range as a finding. A version read is not proof the login path is configured — that part only you can see — and we say so in the report.

What To Do Now

  1. Disable the X/Twitter social login in Jupiter X Core today — or deactivate the plugin if you cannot isolate that feature. There is no patched version to install yet.
  2. Watch Artbees for a fixed release — and read its notes. Do not treat a future update that does not mention CVE-2026-106013 as a fix for it.
  3. Audit the blast radius. Review administrator accounts and recent logins for anything you do not recognize. An auth bypass leaves no failed-login trail, so a clean login log is not evidence nobody came in this way.
  4. When a fix ships, update first, then re-enable the social login — in that order.

The Bigger Lesson for Shipped-Fast Sites

This is the third time in a month we have written up the same failure shape: Qode Membership's Facebook login check tested a misspelled variable and always passed (CVE-2026-92885), Parse Server's custom-adapter validation was never called at all (CVE-2026-116163), and now Jupiter X Core verifies someone — just not the visitor. In every case the authentication code looked complete: the functions exist, the API calls happen, the flow returns a profile. What was missing was the one property that matters — that the identity being trusted is the identity of the person actually signing in.

If your site offers social login, it is authentication code you own even though you didn't write it. Inventory it like you inventory plugins: which providers are enabled, whose app credentials they use, and what account a successful login lands on.

Run the free mini-scan at preshipit.com/free-scan — paste your URL and see the exposures that are visible from outside, including disclosed plugin versions like this one, in about a minute, with a shareable result page. The full scan ($29, one-time) goes deeper: active probing, backend-rule checks, and copy-paste fixes for everything it finds.

Check Jupiter X Core on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Jupiter X Core's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-106013 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Jupiter X Core on your site? Check it against CVE-2026-106013 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Jupiter X Core is in the affected range (≤ 4.61.0), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report