Cyber Resilience

CVE-2024-7772

Artbees Jupiter X Core ≤ 4.6.6

Published
26 September 2024
Modified
02 October 2024
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 72th percentile
Risk Priority 79 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-7772 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Artbees Jupiter X Core. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 28% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Jupiter X Core plugin for WordPress is vulnerable to arbitrary file uploads because of improper file type validation inside the validate function. The flaw affects all versions through 4.6.5 and is tracked as CWE-434. Successful exploitation can allow an attacker to place arbitrary files on the server, which may lead to remote code execution. The issue carries a CVSS 3.1 score of 9.8.

Unauthenticated attackers can exploit the vulnerability over the network without any user interaction or credentials. By sending a crafted request that bypasses the flawed validation, an adversary can upload a malicious file such as a web shell and subsequently execute arbitrary code on the affected WordPress site.

Public references point to a patched version of the plugin released in changeset 3139412 on the WordPress plugin repository. Site administrators are advised to update Jupiter X Core to a release newer than 4.6.5. The current EPSS score of 0.0865 shows no material increase since disclosure.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

The Jupiter X Core plugin for WordPress is vulnerable to arbitrary file uploads due to a mishandled file type validation in the 'validate' function in all versions up to, and including, 4.6.5. This makes it possible for unauthenticated attackers to…

more

upload arbitrary files on the affected site's server which may make remote code execution possible.

CWE(s)
CWE-434

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
attack.mitre.org →
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-38388Same product: Artbees Jupiter X Core
CVE-2025-0365Same product: Artbees Jupiter X Core
CVE-2023-3813Same product: Artbees Jupiter X Core
CVE-2025-0366Same product: Artbees Jupiter X Core
CVE-2025-2105Same product: Artbees Jupiter X Core
CVE-2024-12316Same product: Artbees Jupiter X Core
CVE-2023-38385Same product: Artbees Jupiter X Core
CVE-2024-12033Same product: Artbees Jupiter X Core
CVE-2024-7781Same product: Artbees Jupiter X Core
CVE-2023-38394Same product: Artbees Jupiter X Core

Affected Assets

artbees
jupiter x core
≤ 4.6.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

SI-3 Malicious Code Protection good match

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

CM-7 Least Functionality partial match

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
prevents

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.

A.8.30 Outsourced development partial match
prevents

Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.

A.8.7 Protection against malware partial match
mitigates

Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.

References