CVE-2022-1654

Jupiter Theme <= 6.10.1 and JupiterX Core Plugin <= 2.0.7 - Authenticated Privilege Escalation

2022-05-18 00:00
Ram

Strategic Overview

Status
Patched in 2.0.8
Affected Plugin
Jupiter X Core
Affected Version
<= 2.0.7
CVSS
9.9Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2022-1654
View all Jupiter X Core vulnerabilities

At a glance

CVE-2022-1654 is a critical-severity Improper Privilege Management vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 2.0.7. It carries a CVSS score of 9.9 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 2.0.8; sites on affected versions should update now. Disclosed May 2022, reported by Ram.

Vulnerability Overview

Jupiter Theme <= 6.10.1 and JupiterX Core Plugin <= 2.0.7 allow any authenticated attacker, including a subscriber or customer-level attacker, to gain administrative privileges via the "abb_uninstall_template" (both) and "jupiterx_core_cp_uninstall_template" (JupiterX Core Only) AJAX actions

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-269: Improper Privilege Management

Jupiter X Core <= 2.0.7 carries this weakness at abb_uninstall_template, and reaching it takes any authenticated account. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Jupiter X Core the fix is 2.0.8: builds <= 2.0.7 are affected, anything from 2.0.8 onward is not.

Remediation

Update to version 2.0.8, 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: Jupiter X Core 2.0.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-1654https://www.wordfence.com/threat-intel/vulnerabilities/id/b54f38b6-5f98-469c-802a-a4c1e1f2ab0ehttps://nvd.nist.gov/vuln/detail/CVE-2022-1654

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C