Jupiter X Core <= 2.0.9 - Missing Authorization Checks

2022-08-08 00:00
Anonymous

Strategic Overview

Status
Patched in 2.1.0
Affected Plugin
Jupiter X Core
Affected Version
<= 2.0.9
CVSS
7.6High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Jupiter X Core vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 2.0.9. It carries a CVSS score of 7.6 (reachable over the network; low attack complexity; high confidentiality impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.1.0; sites on affected versions should update now. Disclosed August 2022.

Vulnerability Overview

The JupiterX Core plugin for WordPress suffers from several access control issues in versions up to, and including, 2.0.9. This allows authenticated users to view health check information, import templates, reset the database, create and restore partial database backups, and obtain the paths to created database backups which are protected by an .htaccess file

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.

CWE-862: Missing Authorization

Reaching this weakness in Jupiter X Core <= 2.0.9 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Jupiter X Core the fix is 2.1.0: builds <= 2.0.9 are affected, anything from 2.1.0 onward is not.

Remediation

Update to version 2.1.0, 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.1.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/52daa230-1600-4ace-9adf-3f4e9be51e9f

Related records

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