CVE-2025-2105 Jupiter X Core <= 4.8.11 - Unauthenticated PHP Object Injection via PHAR

High 8.1 Published Updated

Unauthenticated attackers can inject PHP objects via PHAR files in Jupiter X Core, potentially leading to code execution or data theft if a POP chain exists.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-2105?

CVE-2025-2105 is a high-severity unsafe deserialization vulnerability in artbees Jupiter X Core, published on 26 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The Jupiter X Core plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.8.11 via deserialization of untrusted input from the 'file' parameter of the 'raven_download_file' function. This makes it possible for attackers to inject a PHP Object through a PHAR file. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. This vulnerability may be exploited by unauthenticated attackers when a form is present on the site with the file download action, and the ability to upload files is also present. Otherwise, this would be considered exploitable by Contributor-level users and above, because they could create the form needed to successfully exploit this.

Weakness: CWE-502

Which versions are affected by CVE-2025-2105?

It affects 1 product.

Products include Artbees Jupiter X Core.

How do I fix CVE-2025-2105?

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

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2025-2105 being exploited?

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

Sources

Also known as GHSA-4gp3-vjp8-9r2q.

Is CVE-2025-2105 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free