# CVE-2022-1659: JupiterX Core <= 2.0.6 - Information Disclosure, Modification, and Denial of Service

> Unauthenticated attackers can invoke arbitrary functions in the JupiterX Core plugin to read configuration, modify posts, or cause denial of service.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-4qp7-4vpc-hwfm

## What is CVE-2022-1659?

CVE-2022-1659 is a medium-severity missing authorization vulnerability in ArtBees Jupiter X Core, published on 13 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerable versions of the JupiterX Core (<= 2.0.6) plugin register an AJAX action jupiterx_conditional_manager which can be used to call any function in the includes/condition/class-condition-manager.php file by sending the desired function to call in the sub_action parameter. This can be used to view site configuration and logged-in users, modify post conditions, or perform a denial of service attack.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2022-1659?

It affects 1 product.


Products: Artbees Jupiterx.

## How do I fix CVE-2022-1659?

No fix has been published for CVE-2022-1659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1659 being exploited?

There is no known exploitation of CVE-2022-1659 in the wild and no public exploit code.

## Other vulnerabilities in ArtBees Jupiter X Core

- [CVE-2023-32110](https://insights.sbomify.com/CVE-2023-32110/): WordPress JupiterX theme <= 3.0.0 - Auth. Local File Inclusion vulnerability (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1659 and fix it if it is affected.

What it is: CVE-2022-1659 is a medium-severity missing authorization vulnerability in ArtBees Jupiter X Core, published on 13 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1659 in the wild and no public exploit code.

Affected product: ArtBees Jupiter X Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1659/ (Markdown: https://insights.sbomify.com/CVE-2022-1659/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1659
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1659
- OSV: https://osv.dev/vulnerability/CVE-2022-1659

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1659/
Summaries are generated and may contain mistakes; the official description above is the record.