CVE-2026-119219 · Package
NO FIX YET
The Jupiter X Core plugin for WordPress does not sanitize the 'fields[...]' parameter, so injected scripts are saved and stored in pages. When a user opens an affected page, the script runs in their browser.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Jupiter X Core WordPress plugin at version 4.62.0 or earlier. Exposure requires a page or post whose template includes the Raven Author Box widget and whose author can be set to an attacker-registered account, which the description says an administrator can do by reassigning authorship. Sites without this plugin or without that widget can skip it.
Not affected if no-raven-author-box-widget, plugin-not-installed
Who cares jupiter-x-core, self-hosted, wordpress
4.62.0 or earlier is affected per the description).No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.