CVE-2023-3813

Jupiter X Core <= 4.6.6 - Unauthenticated Arbitrary File Download

2023-07-20 00:00
István Márton

Strategic Overview

Status
Patched in 4.6.9
Affected Plugin
Jupiter X Core
Affected Version
<= 4.6.6
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2023-3813
View all Jupiter X Core vulnerabilities

At a glance

CVE-2023-3813 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 4.6.6. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.6.9; sites on affected versions should update now. Disclosed July 2023, reported by István Márton.

Vulnerability Overview

The Jupiter X Core plugin for WordPress is vulnerable to arbitrary file downloads in versions up to, and including, 4.6.6. This makes it possible for unauthenticated attackers to download the contents of arbitrary files on the server, which can contain sensitive information. The requires the premium version of the plugin to be activated. NOTE: This vulnerability was partially patched in version 4.6.5 and fully patched in version 4.6.9.

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.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Jupiter X Core <= 4.6.6 takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Jupiter X Core the fix is 4.6.9: builds <= 4.6.6 are affected, anything from 4.6.9 onward is not.

Remediation

Update to version 4.6.9, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Jupiter X Core 4.6.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-3813https://www.wordfence.com/threat-intel/vulnerabilities/id/f767d94b-fe92-4b69-9d81-96de51e12983https://nvd.nist.gov/vuln/detail/CVE-2023-3813

Related records

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