# CVE-2026-120737: 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 th


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-x3pp-g2j7-pf72

## What is CVE-2026-120737?

CVE-2026-120737 is a medium-severity vulnerability in artbees Jupiter X Core, published on 7 Nov 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

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


## How do I fix CVE-2026-120737?

No fix has been published for CVE-2026-120737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120737 being exploited?

There is no known exploitation of CVE-2026-120737 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120737 and fix it if it is affected.

What it is: CVE-2026-120737 is a medium-severity vulnerability in artbees Jupiter X Core, published on 7 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120737 in the wild and no public exploit code.

Affected product: artbees Jupiter X Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120737/ (Markdown: https://insights.sbomify.com/CVE-2026-120737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120737
- OSV: https://osv.dev/vulnerability/CVE-2026-120737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120737/
Summaries are generated and may contain mistakes; the official description above is the record.
