JupiterX Core <= 4.14.1 - Authenticated (Subscriber+) Missing Authorization To Limited File Upload via Popup Template Import
Strategic Overview
- Status
- Patched in 4.14.2
- Affected Plugin
- Jupiter X Core
- Affected Version
<= 4.14.1- CVSS
- 8.8High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2026-3533
At a glance
CVE-2026-3533 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 4.14.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.14.2; sites on affected versions should update now. Disclosed March 2026, reported by AlexHenry.
Vulnerability Overview
The Jupiter X Core plugin for WordPress is vulnerable to limited file uploads due to missing authorization on import_popup_templates() function as well as insufficient file type validation in the upload_files() function in all versions up to, and including, 4.14.1. This makes it possible for Authenticated attackers with Subscriber-level access and above, to upload files with dangerous types that can lead to Remote Code Execution on servers configured to handle .phar files as executable PHP (e.g., Apache+mod_php), or Stored Cross-Site Scripting via .svg, .dfxp, or .xhtml files upload on any server configuration
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, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Jupiter X Core <= 4.14.1 carries this weakness at import_popup_templates(), and reaching it takes an account at Subscriber level or above. 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 4.14.2: builds <= 4.14.1 are affected, anything from 4.14.2 onward is not.
Remediation
Update to version 4.14.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber 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. 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 4.14.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- 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-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