{
  "id": "CVE-2026-106013",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-106013",
  "published_at": "2026-10-28T01:30:48.32Z",
  "title": "Jupiter X Core \u003c= 4.61.0 - Unauthenticated Authentication Bypass via Twitter/X Social Login oauth_verifier Parameter",
  "vendor": "artbees",
  "product": "Jupiter X Core",
  "cvss": {
    "score": 9.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-287",
  "cvss_by_source": {
    "cna": 9.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "artbees",
        "product": "Jupiter X Core",
        "ranges": [
          "\u003c= 4.61.0"
        ],
        "fixed_in": null
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
