JupiterX Theme <= 3.0.0 - Authenticated Local File Inclusion via print_pane
Strategic Overview
- Status
- Patched in 3.1.0
- Affected Theme
- JupiterX
- Affected Version
<= 3.0.0- CVSS
- 8.1High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2023-32110
At a glance
CVE-2023-32110 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the JupiterX WordPress theme, affecting versions <= 3.0.0. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires an authenticated account. The issue is fixed in version 3.1.0; sites on affected versions should update now. Disclosed May 2023, reported by Rafie Muhammad.
Vulnerability Overview
The JupiterX theme for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 3.0.0 via the print_pane function. This allows authenticated attackers with subscriber-level permissions or above to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
JupiterX <= 3.0.0 carries this weakness at safe, and reaching it takes any authenticated account. 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 JupiterX the fix is 3.1.0: builds <= 3.0.0 are affected, anything from 3.1.0 onward is not.
Remediation
Update to version 3.1.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to JupiterX: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: JupiterX 3.1.0 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C