CVE-2024-7781

Jupiter X Core <= 4.7.5 - Limited Unauthenticated Authentication Bypass to Account Takeover

2024-09-25 16:13
Geo Void

Strategic Overview

Status
Patched in 4.7.8
Affected Plugin
Jupiter X Core
Affected Version
<= 4.7.5
CVSS
8.1High
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2024-7781
View all Jupiter X Core vulnerabilities

At a glance

CVE-2024-7781 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 4.7.5. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.7.8; sites on affected versions should update now. Disclosed September 2024, reported by Geo Void.

Vulnerability Overview

The Jupiter X Core plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 4.7.5. This is due to improper authentication via the Social Login widget. This makes it possible for unauthenticated attackers to log in as the first user to have logged in with a social media account, including administrator accounts. Attackers can exploit the vulnerability even if the Social Login element has been disabled, as long as it was previously enabled and used. The vulnerability was partially patched in version 4.7.5, and fully patched in version 4.7.8.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

Reaching this weakness in Jupiter X Core <= 4.7.5 takes no account at all. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Jupiter X Core the fix is 4.7.8: builds <= 4.7.5 are affected, anything from 4.7.8 onward is not.

Remediation

Update to version 4.7.8, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Jupiter X Core 4.7.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-7781https://www.wordfence.com/threat-intel/vulnerabilities/id/efd279c2-9e95-45bd-9494-fb53a6333c65https://nvd.nist.gov/vuln/detail/CVE-2024-7781

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C