CVE-2023-38389
Published: 21 June 2024
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 6.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-42206
Vulnerability details
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
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Periodic review and update of procedures reduces incorrect authorization implementations over time.
Supervision identifies cases where authorization logic incorrectly permits unauthorized actions.
Defining permitted attribute values and auditing modifications reduces the chance of incorrect authorization outcomes due to tampered or missing labels.
The authorization process and usage restrictions help prevent incorrect authorization for remote access types.
Establishing configuration and connection requirements helps ensure correct rather than incorrect authorization for wireless access.
Establishing connection authorization processes for mobile devices helps ensure authorization decisions are correctly implemented rather than incorrect.
Monitoring account use, notifying on changes, and reviewing accounts for compliance corrects incorrect authorization assignments.
Ensures authorization decisions for external system use are correctly implemented and enforced.