high CVSS 8.1

CVE-2025-2105·PHP vulnerability

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.

Severity
high
Software
PHP
Fixed in
4.8.12
Published
2025-04-26

Affected versions

Until: 4.8.12

Fixed in: 4.8.12

How to fix this CVE

Update the Jupiter X Core WordPress plugin to version 4.8.12 or later to patch the PHP Object Injection vulnerability in the file download handler. This vulnerability allows attackers to deserialize untrusted PHAR files, which could lead to arbitrary code execution if complementary POP chains exist in other installed plugins or themes. Immediately audit your WordPress installation for additional plugins that may contain exploitable gadget chains.

sudo dnf update php -y

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /wp-admin/admin-ajax.php?action=raven_download_file with file parameter containing PHAR:// protocol or base64-encoded serialized PHP objects

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Block or sanitize requests to wp-admin/admin-ajax.php with action=raven_download_file parameter; implement strict input validation to reject file parameters containing PHAR://, serialized object markers (O:, C:), or base64-encoded payloads

How to check if you are affected

  1. Check PHP version: php -v
  2. Verify Jupiter X Core plugin version by examining wp-content/plugins/jupiterx-core/jupiterx-core.php for the Version header or checking the WordPress admin Plugins page
  3. Search web server logs for requests to wp-admin/admin-ajax.php with action=raven_download_file parameter: grep -r 'raven_download_file' /var/log/apache2/ /var/log/nginx/
  4. Confirm patch applied by verifying Jupiter X Core plugin is at version 4.8.12 or later and checking the includes/extensions/raven/includes/utils.php file for secure deserialization handling

FAQ

What is CVE-2025-2105?

CVE-2025-2105 is a PHP Object Injection vulnerability in the Jupiter X Core WordPress plugin that allows attackers to inject malicious PHAR files through the raven_download_file function, potentially enabling code execution if other plugins with exploitable object chains are present.

Is CVE-2025-2105 being actively exploited?

No, CVE-2025-2105 is not currently listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available, though the vulnerability remains serious due to its potential for remote code execution.

What versions of Jupiter X Core are affected by CVE-2025-2105?

All versions up to and including 4.8.11 are vulnerable; version 4.8.12 and later contain the fix.

How do I check if my WordPress site is vulnerable to CVE-2025-2105?

Log into your WordPress admin panel, navigate to Plugins, and verify the Jupiter X Core version number. If it shows 4.8.11 or lower, your site is vulnerable and requires immediate update.

Does Defensia detect CVE-2025-2105?

Yes — Defensia's CVE advisory scanner compares installed plugin versions against the NVD database. If Jupiter X Core is detected on a monitored WordPress installation, CVE-2025-2105 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.
CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.
CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-2105. Free for 1 server.

Get started free