JupiterX Core <= 3.3.5 - Unauthenticated Arbitrary File Upload
Strategic Overview
- Status
- Patched in 3.3.8
- Affected Plugin
- Jupiter X Core
- Affected Version
<= 3.3.5- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2023-38388
At a glance
CVE-2023-38388 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 3.3.5. 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.3.8; 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 arbitrary file uploads in versions up to, and including, 3.3.5 due to missing file type validation on the upload_files() function. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. This affects both free and premium versions 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-434: Unrestricted Upload of File with Dangerous Type
Jupiter X Core <= 3.3.5 carries this weakness at upload_files(), and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Jupiter X Core the fix is 3.3.8: builds <= 3.3.5 are affected, anything from 3.3.8 onward is not.
Remediation
Update to version 3.3.8, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Jupiter X Core 3.3.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
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-2023-38389: JupiterX Core <= 3.3.8 Privilege Escalation
CVE-2023-38389 - 8.8CVE-2025-0366: Jupiter X Core SVG Upload to Local File Inclusion (RCE)
CVE-2025-0366 - 8.3CVE-2023-38385: JupiterX Core 3.0.0 - 3.3.0 Missing Authorization
CVE-2023-38385 - 8.1CVE-2025-2105: Jupiter X Core <= 4.8.11 PHP Object Injection
CVE-2025-2105 - 8.1CVE-2024-7781: Jupiter X Core Limited Unauthenticated Authentication
CVE-2024-7781 - 7.6Jupiter X Core <= 2.0.9 Missing Authorization Checks
- 7.5CVE-2025-50004: JupiterX Core <= 4.10.1 PHP Object Injection
CVE-2025-50004
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C