CVE-2026-120737
Deferred Deferred - Pending Action

Authorization Bypass in Jupiter X Core WordPress Plugin

Publication date: 2026-11-07

Last updated on: 2026-11-07

Assigner: Wordfence

Description
The Jupiter X Core plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.62.0 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to enumerate and render arbitrary published post types not intended for public listing — including Flamingo CF7 submission records containing submitter names, email addresses, phone numbers, full messages, and IP addresses — and perform meta_query boolean-oracle reads against the postmeta of any published post. Exploitation requires that a Posts or Advanced Posts widget on the site has 'Is Archive Template' enabled, which is the standard Jupiter X archive-template configuration used by most Jupiter X sites; additionally, the nonce verified by the second endpoint is minted via wp_create_nonce and printed on every frontend page as ravenTools.nonce, rendering it ineffective as an authorization barrier.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-07
Last Modified
2026-11-07
Generated
2026-11-07
AI Q&A
2026-11-07
EPSS Evaluated
N/A
NVD
CVE-2026-120737
EUVD
EUVD-2026-118557

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
artbees Jupiter X Core From 0 (inc) to 4.62.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Jupiter X Core WordPress plugin up to version 4.62.0 has an authorization bypass flaw. It fails to properly verify user permissions before allowing actions. This lets unauthenticated attackers access restricted content like Flamingo CF7 form submissions containing personal data (names, emails, phone numbers, messages, IP addresses). Attackers can also query post metadata using a boolean-oracle technique.

Detection Guidance

Check for unauthorized access to Flamingo CF7 submission records or arbitrary post types by reviewing server logs for unusual requests targeting Jupiter X endpoints. Look for GET or POST requests to /wp-json/raven/v1/ endpoints with the ravenTools.nonce parameter. Inspect WordPress widgets for 'Is Archive Template' enabled in Jupiter X sites.

Impact Analysis

If exploited, attackers can steal sensitive user data submitted via contact forms. They may also gather metadata from posts, potentially exposing additional information. The attack is possible on most Jupiter X sites due to default archive-template configurations enabling the vulnerable widget.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR and HIPAA requirements for data protection and access controls. Organizations using affected Jupiter X versions may face compliance violations and potential fines if exploited.

Mitigation Strategies

Update the Jupiter X Core plugin to the latest version beyond 4.62.0. Disable the 'Is Archive Template' option in Posts or Advanced Posts widgets if enabled. Review and restrict access to sensitive data like Flamingo CF7 submissions. Implement additional authentication checks for wp-json/raven/v1/ endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120737. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...