Jupiter X Core: A security weakness
Jupiter X Core is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Jupiter X Core
- Plugin slug
jupiter-x-core- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jan 07, 2025
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jan 07, 2025 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
Update Jupiter X Core to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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 / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N