CVE-2025-2105

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

2025-04-25 17:04
Phat RiO

Strategic Overview

Status
Patched in 4.8.12
Affected Plugin
Jupiter X Core
Affected Version
<= 4.8.11
CVSS
8.1High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2025-2105
View all Jupiter X Core vulnerabilities

At a glance

CVE-2025-2105 is a high-severity Deserialization of Untrusted Data vulnerability in the Jupiter X Core WordPress plugin, affecting versions <= 4.8.11. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.8.12; sites on affected versions should update now. Disclosed April 2025, reported by Phat RiO.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Jupiter X Core <= 4.8.11 carries this weakness at file, and reaching it takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Jupiter X Core the fix is 4.8.12: builds <= 4.8.11 are affected, anything from 4.8.12 onward is not.

Remediation

Update to version 4.8.12, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Jupiter X Core 4.8.12 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

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