JupiterX Theme <= 2.0.6 and JupiterX Core <= 2.0.6 - Authenticated Arbitrary Plugin Deactivation and Settings Modification
Strategic Overview
- Status
- Patched in 2.0.7
- Affected Theme
- JupiterX
- Affected Version
<= 2.0.6- CVSS
- 6.5Medium
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE-2022-1656
At a glance
CVE-2022-1656 is a medium-severity Improper Access Control vulnerability in the JupiterX WordPress theme, affecting versions <= 2.0.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account. The issue is fixed in version 2.0.7; sites on affected versions should update now. Disclosed May 2022, reported by Ram.
Vulnerability Overview
Vulnerable versions of the JupiterX Theme allow any logged-in user, including subscriber-level users, to access any of the functions registered in lib/api/api/ajax.php, which also grant access to the jupiterx_api_ajax_ actions registered by the JupiterX Core Plugin. This includes the ability to deactivate arbitrary plugins as well as update the theme’s API key.
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 integrity.
CWE-284: Improper Access Control
Reaching this weakness in JupiterX <= 2.0.6 takes any authenticated account. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For JupiterX the fix is 2.0.7: builds <= 2.0.6 are affected, anything from 2.0.7 onward is not.
Remediation
Update to version 2.0.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: JupiterX 2.0.7 closes this, and updating the theme is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C