CVE-2023-38389

JupiterX Core <= 3.3.8 - Unauthenticated Privilege Escalation

2023-08-22 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.4.3
Affected Plugin
Jupiter X Core
Affected Version
<= 3.3.8
CVSS
9.8Critical
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2023-38389
View all Jupiter X Core vulnerabilities

At a glance

CVE-2023-38389 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 3.3.8. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.4.3; sites on affected versions should update now. Disclosed August 2023, reported by Rafie Muhammad.

Vulnerability Overview

The JupiterX Core plugin for WordPress is vulnerable to privilege escalation due to insufficient validation in versions up to, and including, 3.3.8 due to insufficient controls on the facebook_log_user_in() function. This makes it possible for unauthenticated attackers to stage a site takeover. Please note that this affects both the free and premium version of the plugin.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, 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

Jupiter X Core <= 3.3.8 carries this weakness at facebook_log_user_in(), and reaching it 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 3.4.3: builds <= 3.3.8 are affected, anything from 3.4.3 onward is not.

Remediation

Update to version 3.4.3, 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 3.4.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-38389https://www.wordfence.com/threat-intel/vulnerabilities/id/b894473b-b2ed-475b-892e-603db609f88ahttps://nvd.nist.gov/vuln/detail/CVE-2023-38389

Related records

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