# CVE-2025-0366: Jupiter X Core <= 4.8.7 - Authenticated (Contributor+) SVG Upload to Local File Inclusion (Remote Code Execution)

> Authenticated contributors can upload malicious SVG files to achieve remote code execution via local file inclusion in Jupiter X Core.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pq7v-v662-6pp7

## What is CVE-2025-0366?

CVE-2025-0366 is a high-severity vulnerability in artbees Jupiter X Core, published on 1 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Jupiter X Core plugin for WordPress is vulnerable to Local File Inclusion to Remote Code Execution in all versions up to, and including, 4.8.7 via the get_svg() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution. In this specific case,  an attacker can create a form that allows SVG uploads, upload an SVG file with malicious content and then include the SVG file in a post to achieve remote code execution. This means it is relatively easy to gain remote code execution as a contributor-level user and above by default.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2025-0366?

It affects 1 product.


Products: Artbees Jupiter X Core.

## How do I fix CVE-2025-0366?

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

## Is CVE-2025-0366 being exploited?

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

## Other vulnerabilities in artbees Jupiter X Core

- [CVE-2024-7772](https://insights.sbomify.com/CVE-2024-7772/): Jupiter X Core <= 4.6.5 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2023-38389](https://insights.sbomify.com/CVE-2023-38389/): WordPress Jupiter X Core plugin <= 3.3.8 - Unauthenticated Account Takeover vulnerability (critical 9.8)
- [CVE-2023-38388](https://insights.sbomify.com/CVE-2023-38388/): WordPress Jupiter X Core plugin <= 3.3.5 - Unauth. Arbitrary File Upload vulnerability (critical 9.0)
- [CVE-2023-38385](https://insights.sbomify.com/CVE-2023-38385/): WordPress Jupiter X Core plugin <= 3.3.0 - Multiple Auth. Broken Access Control vulnerability (high 8.3)
- [CVE-2025-2105](https://insights.sbomify.com/CVE-2025-2105/): Jupiter X Core <= 4.8.11 - Unauthenticated PHP Object Injection via PHAR (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0366 and fix it if it is affected.

What it is: CVE-2025-0366 is a high-severity vulnerability in artbees Jupiter X Core, published on 1 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0366 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-2025-0366/ (Markdown: https://insights.sbomify.com/CVE-2025-0366/index.md)
```

## Sources

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

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