Jupiter X Core <= 4.62.0 - Missing Authorization to Unauthenticated Limited File Download via 'file' Parameter
Strategic Overview
- Status
- Patched in 4.63.0
- Affected Plugin
- Jupiter X Core
- Affected Version
<= 4.62.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-120555
At a glance
CVE-2026-120555 is a medium-severity Missing Authorization vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 4.62.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.63.0; sites on affected versions should update now. Disclosed November 2026, reported by VARVEL (varvel).
Vulnerability Overview
The Jupiter X Core plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.62.0 via the 'file' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The path confinement check introduced in the CVE-2023-3813 fix (strpos + realpath) is present and working, so reads are confined to wp-content/uploads/ and cannot reach wp-config.php or other files outside that directory.
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.
CWE-862: Missing Authorization
Jupiter X Core <= 4.62.0 carries this weakness at file, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Jupiter X Core the fix is 4.63.0: builds <= 4.62.0 are affected, anything from 4.63.0 onward is not.
Remediation
Update to version 4.63.0, 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.63.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Jupiter X Core
- 9.9CVE-2022-1654: Jupiter Theme and JupiterX Core Plugin <= 2.0.7
CVE-2022-1654 - 9.8CVE-2026-106013: Jupiter X Core <= 4.61.0 Authentication Bypass
CVE-2026-106013 - 9.8CVE-2024-7772: Jupiter X Core <= 4.6.5 Arbitrary File Upload
CVE-2024-7772 - 9.8CVE-2023-38388: JupiterX Core <= 3.3.5 Arbitrary File Upload
CVE-2023-38388 - 9.8CVE-2023-38389: JupiterX Core <= 3.3.8 Privilege Escalation
CVE-2023-38389 - 8.8CVE-2026-3533: JupiterX Core <= 4.14.1 Limited File Upload
CVE-2026-3533 - 8.8CVE-2025-0366: Jupiter X Core SVG Upload to Local File Inclusion (RCE)
CVE-2025-0366 - 8.1CVE-2025-2105: Jupiter X Core <= 4.8.11 PHP Object Injection
CVE-2025-2105
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C