CVE-2026-39491: JupiterX Core (WordPress plugin) · Cross-site Scripting
Affects JupiterX Core (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| artbeesJupiterX Core | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, limit subscriber privileges where possible and monitor for suspicious activity related to script injection. Avoid granting unnecessary user rights that could be leveraged to exploit this vulnerability.
Description
CVE-2026-39491 is a medium severity cross-site scripting (XSS) vulnerability in artbees JupiterX Core affecting versions up to and including 4.14.1. The issue involves improper neutralization of input during web page generation, allowing a subscriber-level user to potentially execute malicious scripts. This vulnerability has a CVSS score of 6.5, indicating a moderate impact on confidentiality, integrity, and availability. No official patch or remediation guidance has been provided yet, and there are no known exploits in the wild.