First published: Sat Feb 01 2025(Updated: )
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.
Credit: security@wordfence.com
Affected Software | Affected Version | How to fix |
---|---|---|
Artbees Jupiter X Core | <=4.8.7 | |
Jupiter X Core | <4.8.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-0366 is considered a critical severity vulnerability due to its potential for remote code execution.
To fix CVE-2025-0366, update the Jupiter X Core plugin to the latest version that is not affected by this vulnerability.
Authenticated users with Contributor-level access and above using versions up to and including 4.8.7 of the Jupiter X Core plugin are affected by CVE-2025-0366.
CVE-2025-0366 is classified as a Local File Inclusion vulnerability that can lead to Remote Code Execution.
The get_svg() function in the Jupiter X Core plugin is responsible for the CVE-2025-0366 vulnerability.