# CVE-2026-106013: Jupiter X Core <= 4.61.0 - Unauthenticated Authentication Bypass via Twitter/X Social Login oauth_verifier Parameter


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-5x75-7jgc-v7c2

## What is CVE-2026-106013?

CVE-2026-106013 is a critical vulnerability in artbees Jupiter X Core, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-106013?


## How do I fix CVE-2026-106013?

No fix has been published for CVE-2026-106013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106013 being exploited?

There is no known exploitation of CVE-2026-106013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106013 and fix it if it is affected.

What it is: CVE-2026-106013 is a critical vulnerability in artbees Jupiter X Core, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106013 in the wild and no public exploit code.

Affected product: artbees Jupiter X Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106013/ (Markdown: https://insights.sbomify.com/CVE-2026-106013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106013
- OSV: https://osv.dev/vulnerability/CVE-2026-106013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106013/
Summaries are generated and may contain mistakes; the official description above is the record.