# CVE-2026-120555: Jupiter X Core <= 4.62.0 - Missing Authorization to Unauthenticated Limited File Download via 'file' Parameter


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-p3jv-9gww-63p2

## What is CVE-2026-120555?

CVE-2026-120555 is a medium-severity vulnerability in artbees Jupiter X Core, published on 7 Nov 2026. 

### Official description

The Jupiter X Core plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.62.0 via the 'file' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The path confinement check introduced in the CVE-2023-3813 fix (strpos + realpath) is present and working, so reads are confined to wp-content/uploads/ and cannot reach wp-config.php or other files outside that directory.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-120555?


## How do I fix CVE-2026-120555?

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

## Is CVE-2026-120555 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120555 and fix it if it is affected.

What it is: CVE-2026-120555 is a medium-severity vulnerability in artbees Jupiter X Core, published on 7 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120555 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-2026-120555/ (Markdown: https://insights.sbomify.com/CVE-2026-120555/index.md)
```

## Sources

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

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