LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38389: WordPress Jupiter X Core plugin <= 3.3.8 - Unauthenticated Account Takeover vulnerability

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-38389 is a critical authorization flaw in the WordPress JupiterX Core plugin through 3.3.8. Public source data describes unauthenticated account takeover risk, meaning a public website using the affected plugin could expose site control without a valid login.

Executive priority

Treat this as an urgent WordPress exposure issue. Public sites using the affected plugin could face account takeover risk without attacker credentials, so prioritize inventory, vendor-guided remediation, and account integrity review.

Technical view

The CVE describes CWE-863 incorrect authorization in Artbees JupiterX Core, allowing functionality access not properly constrained by ACLs. It affects JupiterX Core through 3.3.8 and carries CVSS 3.1 9.8: network-accessible, low complexity, no privileges, no user interaction, high impact.

Likely exposure

Exposure is most likely on internet-facing WordPress sites running JupiterX Core version 3.3.8 or earlier. The source bundle does not provide CPEs or hosting-specific indicators, so inventory must be plugin-based.

Exploitation context

The provided data does not show CISA KEV listing or cited evidence of active exploitation. However, the CVSS vector and Patchstack title indicate unauthenticated account takeover potential, which makes exposed public WordPress sites urgent to assess.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. The CVE states incorrect authorization and ACL failure, but the provided sources do not include patch version details, exploit proof, or active exploitation confirmation.

Mitigation direction

  • Inventory all WordPress sites for JupiterX Core plugin usage.
  • Check installed JupiterX Core versions against the affected range through 3.3.8.
  • Follow Artbees or Patchstack guidance for the fixed release or mitigation.
  • Disable or remove the plugin where vendor remediation cannot be applied promptly.
  • Review administrator accounts and recent account changes for unauthorized activity.

Validation and detection

  • Confirm each WordPress instance has no JupiterX Core version through 3.3.8.
  • Verify public sites are not running the vulnerable plugin before normal operation resumes.
  • Review WordPress users for unexpected administrators, email changes, or password resets.
  • Check access logs and security events for suspicious unauthenticated account-management activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-38389 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-38389Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ArtbeesJupiterX Coren/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.