Security Resilience

CVE-2023-38389

Access Control in Artbees Jupiter X Core ≤ 3.3.8

Published
21 June 2024
Modified
21 November 2024
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.014 72th percentile
Risk Priority 81 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-2023-38389 is a critical-severity Incorrect Authorization (CWE-863) vulnerability in Artbees Jupiter X Core. Its CVSS base score is 9.8 (Critical).

Operationally, 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 AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — 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.

CVE-2023-38389 is an incorrect authorization vulnerability (CWE-863) in the Artbees JupiterX Core plugin for WordPress. The flaw affects all versions through 3.3.8 and permits access to functionality that is not properly constrained by ACLs, producing a CVSS 3.1 base score of 9.8 under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Unauthenticated remote attackers can exploit the weakness to achieve account takeover without any user interaction or credentials. The issue was disclosed on 21 June 2024 and is tracked by Patchstack as an unauthenticated account takeover in the Jupiter X Core plugin at version 3.3.0.

The current and peak EPSS values are both 0.1185, indicating a stable rather than rising exploitation probability after public disclosure. No additional real-world exploitation data or AI/ML relevance is reported in the available sources.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Incorrect Authorization vulnerability in Artbees JupiterX Core allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects JupiterX Core: from n/a through 3.3.8.

CWE(s)

Related Threats

CVEs Like This One

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

Affected Assets

artbees
jupiter x core
≤ 3.3.8

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.

AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.

A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.

Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.

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.

blocks

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

blocks

A.5.18's provisioning, revocation, review and adjustment of access rights (incl. before role changes/termination, with segregation and owner approval) directly stops incorrect authorization decisions from being exploitable in the vast majority of cases; the bounded remainder is incorrectness inside the authorization logic itself (e.g. flawed conditional or missing check) rather than rights that were wrongly granted.

blocks

A.8.3 directly mandates restricting access to information per policies via configuration, identity/group controls, isolation, and dynamic techniques that enforce correct authorization decisions, addressing most but not all slices of CWE-863 (e.g., remainder in non-access-decision authorization errors like timing or environmental factors).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-863, a class-level weakness, and none of its children carries one either.

References