LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38388: WordPress Jupiter X Core plugin <= 3.3.5 - Unauth. Arbitrary File Upload vulnerability

Unrestricted Upload of File with Dangerous Type vulnerability in Artbees JupiterX Core.This issue affects JupiterX Core: from n/a through 3.3.5.

CriticalCVSS 9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-38388 is a critical WordPress plugin flaw in Artbees JupiterX Core through 3.3.5. An unauthenticated attacker could upload a dangerous file type, potentially leading to full site compromise. Public sources do not show confirmed active exploitation or a named fixed version in the provided bundle.

Executive priority

Treat this as urgent for any public WordPress property using JupiterX Core. The business risk is website takeover, defacement, data exposure, or service disruption. Prioritize inventory first, then patch or disable affected installations.

Technical view

The issue is CWE-434: unrestricted upload of a file with a dangerous type. It affects Artbees JupiterX Core through 3.3.5 and has CVSS 3.1 score 9.0 with PR:N and UI:N. Attack complexity is listed as high, but impact spans confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely on internet-facing WordPress sites using JupiterX Core version 3.3.5 or earlier. The affected CPE data is incomplete, so teams should validate by plugin inventory rather than relying only on scanner CPE matching.

Exploitation context

The CVE record and Patchstack entry describe unauthenticated arbitrary file upload risk. The provided bundle marks KEV as false and gives no cited evidence of active exploitation, exploit maturity, or in-the-wild abuse.

Researcher notes

Do not assume exploitation from the provided evidence. The CVSS vector indicates unauthenticated network attack with high complexity and changed scope. The main uncertainty is remediation detail: the bundle names affected versions through 3.3.5 but does not provide a specific fixed release.

Mitigation direction

  • Identify all WordPress sites using Artbees JupiterX Core.
  • Check Artbees and Patchstack guidance for an updated safe version.
  • Update JupiterX Core where a vendor-supported fix is available.
  • Temporarily disable the plugin if no safe update path is available.
  • Restrict administrative and file-management access while remediation is pending.
  • Review web server protections for dangerous upload handling.

Validation and detection

  • Confirm installed JupiterX Core versions across production and staging.
  • Flag any instance running version 3.3.5 or earlier.
  • Verify remediation by rechecking the plugin version after update or removal.
  • Review recent uploads for unexpected executable or script-like files.
  • Review web and application logs for suspicious unauthenticated upload 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-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-38388 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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
9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.