Skip to content
Sign in
CVE-2025-21058.1HighCWE-502

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

artbees · Jupiter X Core

Affected: artbees Jupiter X Core · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.8%probability of exploitation in the next 30 days
56th percentile
050100

Higher than 56% of scored CVEs

8.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • artbees · Jupiter X Coreup to and including 4.8.11

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
artbees
Published
April 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-2105 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in