Read the docs

Stored cross-site scripting in Jupiter X Core WordPress plugin

Priority LOW 24CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.

Summary

The Jupiter X Core plugin for WordPress up to and including 4.62.0 does not sanitize or escape custom user meta fields submitted through Raven Register, a stored cross-site scripting flaw (CWE-79). An unauthenticated attacker can register an account and store script in these fields. The script runs when a user opens a page or post authored by that account that includes the Raven Author Box widget, which requires an administrator to assign authorship to the attacker's account.

Written with Claude Haiku 5.5 from the sources below · 2026-11-07

Description from the CNA

The Jupiter X Core plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fields[<custom_meta_field_id>]' parameter in all versions up to, and including, 4.62.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Execution requires that the attacker-registered account be assigned as the post_author of a page or post whose template includes the Raven Author Box widget, a fixture an administrator can create by reassigning authorship to any user including newly registered Subscribers.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00253 16th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
artbeesJupiter X Coreup to 4.62.0—No fix listedCNA
  • Jupiter X Core Vendorartbees Affected up to 4.62.0 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:artbees:jupiter_x_core:*:*:*:*:*:*:*:*——artbees
  • cpe:2.3:a:artbees:jupiter_x_core:*:*:*:*:*:*:*:* Versions — — ·artbees

Remediation

The sources list no fixed version for Jupiter X Core.

Written with Claude Haiku 5.5 from the sources below · 2026-11-07

Timeline

  1. 2026-11-07 Threatist record created from CVE-2026-119219
  2. 2026-11-07 Alias added: GHSA-h4rp-mgwv-m8h3
  3. 2026-11-07 CISA SSVC decision points changed
  4. 2026-11-07 Priority changed: MEDIUM → LOW

References

  • TI-2024-07206 Jupiter X Core <= 4.6.5 - Unauthenticated Arbitrary File Upload CVSS 3.1CRITICAL 9.8
  • TI-2026-81637 Authentication bypass in Jupiter X Core WordPress plugin via X login CVSS 3.1CRITICAL 9.8
  • TI-2023-19772 WordPress Jupiter X Core plugin <= 3.3.5 - Unauth. Arbitrary File Upload vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2024-07214 Jupiter X Core <= 4.7.5 - Limited Unauthenticated Authentication Bypass to Account Takeover CVSS 3.1CRITICAL 9.8
  • TI-2023-19773 WordPress Jupiter X Core plugin <= 3.3.8 - Unauthenticated Account Takeover vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2025-00298 Jupiter X Core <= 4.8.7 - Authenticated (Contributor+) SVG Upload to Local File Inclusion (Remote Code Execution) CVSS 3.1HIGH 8.8
See all 31 →

Sources