Jupiter X Core <= 4.61.0 — Unauthenticated Authentication Bypass via Twitter/X Social Login oauth_verifier Parameter
CVE-2026-106013Published · Updated Action summary
Affected: ≤4.61.0Update to 4.62.0 or newer
All remediation steps- Severity
- Critical9.8
- CVSS
- 9.8CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
- Weakness
- CWE-287 Improper Authentication
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Jupiter X Core jupiterx-core
- Affected≤ 4.61.0
- Patched in4.62.0
Update to 4.62.0 or newer.
You are affected if you run ≤ 4.61.0. Version 4.62.0 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Jupiter X Core.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 4.62.0, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Jupiter X Core to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to daroo.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Jupiter X Core
All 28| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Missing Authorization to Unauthenticated Limited File Download via 'file' Parameter ≤4.62.0Update to 4.63.0 | CVE-2026-120555 | |
| Medium5.9 | Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'archive_query' Parameter ≤4.62.0Update to 4.63.0 | CVE-2026-120737 | |
| Medium5.4 | Unauthenticated Stored Cross-Site Scripting via Raven Register Custom User Meta ≤4.62.0Update to 4.63.0 | CVE-2026-119219 | |
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting via 'forget_password_link' Parameter ≤4.61.0Update to 4.62.0 | CVE-2026-10511 | |
| Medium5.3 | Missing Authorization ≤4.14.1Update to 4.14.2 | CVE-2026-39490 |
- Medium5.3Missing Authorization to Unauthenticated Limited File Download via 'file' Parameter
≤4.62.0Update to 4.63.0
- Medium5.9Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'archive_query' Parameter
≤4.62.0Update to 4.63.0
- Medium5.4Unauthenticated Stored Cross-Site Scripting via Raven Register Custom User Meta
≤4.62.0Update to 4.63.0
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'forget_password_link' Parameter
≤4.61.0Update to 4.62.0
- Medium5.3Missing Authorization
≤4.14.1Update to 4.14.2
Timeline
CVE published
Severity critical, CVSS 9.8
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.