# CVE-2024-7781: Jupiter X Core <= 4.7.5 - Limited Unauthenticated Authentication Bypass to Account Takeover

> Unauthenticated attackers can bypass authentication via the Social Login widget to take over administrator accounts in Jupiter X Core.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qm25-6w48-7h5h

## What is CVE-2024-7781?

CVE-2024-7781 is a high-severity authentication bypass vulnerability in artbees Jupiter X Core, published on 26 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Jupiter X Core plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 4.7.5. This is due to improper authentication via the Social Login widget. This makes it possible for unauthenticated attackers to log in as the first user to have logged in with a social media account, including administrator accounts. Attackers can exploit the vulnerability even if the Social Login element has been disabled, as long as it was previously enabled and used. The vulnerability was partially patched in version 4.7.5, and fully patched in version 4.7.8.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2024-7781?

It affects 1 product.


Products: Artbees Jupiter X Core.

## How do I fix CVE-2024-7781?

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

## Is CVE-2024-7781 being exploited?

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

## Other vulnerabilities in artbees Jupiter X Core

- [CVE-2024-7772](https://insights.sbomify.com/CVE-2024-7772/): Jupiter X Core <= 4.6.5 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2023-38389](https://insights.sbomify.com/CVE-2023-38389/): WordPress Jupiter X Core plugin <= 3.3.8 - Unauthenticated Account Takeover vulnerability (critical 9.8)
- [CVE-2023-38388](https://insights.sbomify.com/CVE-2023-38388/): WordPress Jupiter X Core plugin <= 3.3.5 - Unauth. Arbitrary File Upload vulnerability (critical 9.0)
- [CVE-2025-0366](https://insights.sbomify.com/CVE-2025-0366/): Jupiter X Core <= 4.8.7 - Authenticated (Contributor+) SVG Upload to Local File Inclusion (Remote Code Execution) (high 8.8)
- [CVE-2023-38385](https://insights.sbomify.com/CVE-2023-38385/): WordPress Jupiter X Core plugin <= 3.3.0 - Multiple Auth. Broken Access Control vulnerability (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7781 and fix it if it is affected.

What it is: CVE-2024-7781 is a high-severity authentication bypass vulnerability in artbees Jupiter X Core, published on 26 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7781 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-2024-7781/ (Markdown: https://insights.sbomify.com/CVE-2024-7781/index.md)
```

## Sources

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

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