HomeWordPress vulnerabilitiesJupiter X Core
Jupiter X Core vulnerabilities
Jupiter X Core has 10 known vulnerabilities in this database. The most recent published record is dated 24 Mar 2026.
- Known vulnerabilities
- 10
- Active installs
- 70,000+
- Latest version
- 4.60.0
- Last updated
- 17 Aug 2026
- Most recent
- 24 Mar 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-3533 | High 8.8 | Up to 4.14.1 | Fixed in a later version (latest 4.60.0) | 24 Mar 2026 |
| Cross-site scripting (XSS) CVE-2025-3888 | Medium 6.4 | Up to 4.8.12 | Fixed in a later version (latest 4.60.0) | 17 May 2025 |
| PHP object injection CVE-2025-2105 | High 8.1 | Before 4.8.12 | Fixed in 4.8.12 | 26 Apr 2025 |
| Path traversal CVE-2025-0365 | Medium 6.5 | Before 4.8.8 | Fixed in 4.8.8 | 1 Feb 2025 |
| Remote code execution CVE-2025-0366 | High 8.8 | Before 4.8.8 | Fixed in 4.8.8 | 1 Feb 2025 |
| Broken access control CVE-2024-12316 | Medium 5.3 | Before 4.8.6 | Fixed in 4.8.6 | 7 Jan 2025 |
| Broken access control CVE-2024-12033 | Medium 4.3 | Before 4.8.6 | Fixed in 4.8.6 | 7 Jan 2025 |
| Remote code execution CVE-2024-7772 | Critical 9.8 | Before 4.6.6 | Fixed in 4.6.6 | 26 Sep 2024 |
| Authentication bypass CVE-2024-7781 | High 8.1 | Before 4.7.8 | Fixed in 4.7.8 | 26 Sep 2024 |
| Arbitrary file read CVE-2023-3813 | High 7.5 | Up to 2.5.0 | Fixed in a later version (latest 4.60.0) | 21 Jul 2023 |
Read the published descriptions
- CVE-2026-3533, 24 Mar 2026
- The Jupiter X Core plugin for WordPress is vulnerable to limited file uploads due to missing authorization on import_popup_templates() function as well as insufficient file type validation in the upload_files() function in all versions up to, and including, 4.14.1. This makes it possible for Authenticated attackers with Subscriber-level access and above, to upload files with dangerous types that can lead to Remote Code Execution on servers configured to handle .phar files as executable PHP (e.g., Apache+mod_php), or Stored Cross-Site Scripting via .svg, .dfxp, or .xhtml files upload on any server configuration CVE record
- CVE-2025-3888, 17 May 2025
- The Jupiter X Core plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File inclusion in all versions up to, and including, 4.8.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the page with the included SVG file. CVE record
- CVE-2025-2105, 26 Apr 2025
- 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. CVE record
- CVE-2025-0365, 1 Feb 2025
- The Jupiter X Core plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.8.7 via the inline SVG feature. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. CVE record
- CVE-2025-0366, 1 Feb 2025
- 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. CVE record
- CVE-2024-12316, 7 Jan 2025
- The Jupiter X Core plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the export_popup_action() function in all versions up to, and including, 4.8.5. This makes it possible for unauthenticated attackers to export popup templates. CVE record
- CVE-2024-12033, 7 Jan 2025
- The Jupiter X Core plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the sync_libraries() function in all versions up to, and including, 4.8.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to sync libraries CVE record
- CVE-2024-7772, 26 Sep 2024
- The Jupiter X Core plugin for WordPress is vulnerable to arbitrary file uploads due to a mishandled file type validation in the 'validate' function in all versions up to, and including, 4.6.5. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2024-7781, 26 Sep 2024
- The Jupiter X Core plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 4.7.5. This is due to improper authentication via the Social Login widget. This makes it possible for unauthenticated attackers to log in as the first user to have logged in with a social media account, including administrator accounts. Attackers can exploit the vulnerability even if the Social Login element has been disabled, as long as it was previously enabled and used. The vulnerability was partially patched in version 4.7.5, and fully patched in version 4.7.8. CVE record
- CVE-2023-3813, 21 Jul 2023
- The Jupiter X Core plugin for WordPress is vulnerable to arbitrary file downloads in versions up to, and including, 4.6.6. This makes it possible for unauthenticated attackers to download the contents of arbitrary files on the server, which can contain sensitive information. The requires the premium version of the plugin to be activated. NOTE: This vulnerability was partially patched in version 4.6.5 and fully patched in version 4.6.9. CVE record
What to do if you run Jupiter X Core
If you run Jupiter X Core, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Jupiter X Core vulnerabilities
Free. We email you when a new vulnerability is published for Jupiter X Core, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.