CVE-2025-0365

Jupiterx Core <= 4.8.7 - Authenticated (Contributor+) Arbitrary File Read

2025-01-31 00:00
stealthcopter

Strategic Overview

Status
Patched in 4.8.8
Affected Plugin
Jupiter X Core
Affected Version
<= 4.8.7
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-0365
View all Jupiter X Core vulnerabilities

At a glance

CVE-2025-0365 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 4.8.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.8.8; sites on affected versions should update now. Disclosed January 2025, reported by stealthcopter.

Vulnerability Overview

The Jupiter X Core plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.8.7 via the inline SVG feature. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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 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.8.7 takes an account at Contributor level or above. 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.8.8: builds <= 4.8.7 are affected, anything from 4.8.8 onward is not.

Remediation

Update to version 4.8.8, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Jupiter X Core 4.8.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-0365https://www.wordfence.com/threat-intel/vulnerabilities/id/d3bc5ef7-6825-463f-a3ce-d6ab1fc0e030https://nvd.nist.gov/vuln/detail/CVE-2025-0365

Related records

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