CVE-2026-106013
Last modified
CVE-2026-106013 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 0.55% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| artbees | Jupiter X Core | <= 4.61.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-106013?
How severe is CVE-2026-106013?
How do I fix CVE-2026-106013?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-106002The Court Reservation WordPress plugin before 1.12.4 does n…5.3
- CVE-2026-106003The Court Reservation WordPress plugin before 1.12.4 does n…5.3
- CVE-2026-106004The DT LMS WordPress plugin through 1.2 does not perform ca…5.3
- CVE-2026-106006Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-10601A user with Viewer permissions can use specially crafted req…4.3
- CVE-2026-106010The BDM Digital Payment Gateway WordPress plugin through 1.3…5.3
- CVE-2026-106014The Gateway for Vantiv on WC WordPress plugin through 1.0.1 …5.3
- CVE-2026-106016Mitigation bypass in the File Handling component. This vulne…9.8
- CVE-2026-106017Improper certificate validation in the OpenVPN 3 Core librar…6.3
- CVE-2026-106019Insertion of sensitive information into log file vulnerabili…8.8
- CVE-2026-106020Improper neutralization of input used for LLM prompting vuln…8.6
- CVE-2026-106022Cleartext storage of sensitive information in memory vulnera…8.6
Are you affected by CVE-2026-106013?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
