Skip to content
A detailed explainer is available in Japanese. Read the Japanese explainer
Critical 9.8

Jupiter X Coreの認証回避の脆弱性、4.61.0以前が対象

CVE-2026-106013 First seen on SecPulse

Summary

WordPressプラグインのJupiter X Coreに、Xのソーシャルログインを悪用して認証なしで管理者になりすませる脆弱性が見つかりました。4.61.0以前を使うサイトが対象です。版の確認と更新を済ませ、更新できない間はXでのログイン機能を止めてください。

AI summary

Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.

WordPressプラグインのJupiter X Coreに、Xのソーシャルログインを悪用して認証なしで管理者になりすませる脆弱性が見つかりました。4.61.0以前を使うサイトが対象です。版の確認と更新を済ませ、更新できない間はXでのログイン機能を止めてください。

Affected packages

EcosystemPackageAffectedFixed
artbees Jupiter X Core
≤ 4.61.0
—
Original description The description as published by the source.

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.

Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details