Security readout for executives and security teams
Plain-English summary
CVE-2023-3813 lets unauthenticated visitors download arbitrary server files from vulnerable Jupiter X Core WordPress plugin installations. The business risk is exposure of sensitive files, configuration data, or credentials. Sources say exploitation requires the premium version of the plugin to be activated, and the issue was fully patched in 4.6.9.
Executive priority
Treat this as a high-priority confidentiality issue for affected WordPress sites. Prioritize internet-facing sites and environments where WordPress configuration files could expose database credentials or other secrets. There is no cited active exploitation, but the unauthenticated nature makes remediation time-sensitive.
Technical view
The flaw is an unauthenticated arbitrary file download in Jupiter X Core up to and including 4.6.6, mapped to CWE-22. CVSS 3.1 is 7.5 because network attackers need no credentials or user interaction and confidentiality impact is high. WordPress Trac references show changes in the affected Raven utility code and the 4.6.9 patched file.
Likely exposure
Exposure is likely limited to WordPress sites running the Jupiter X Core plugin with the premium version activated, especially versions at or below 4.6.6. The source notes a partial patch in 4.6.5 and a full patch in 4.6.9, so older or uncertain deployments need review.
Exploitation context
The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The weakness is still serious because it is unauthenticated, network-accessible, low-complexity, and can reveal sensitive server-side files. No exploit steps are needed to justify urgent remediation.
Researcher notes
Evidence supports CWE-22 arbitrary file download in Jupiter X Core. The description states affected versions through 4.6.6, premium activation required, partial patch in 4.6.5, and full patch in 4.6.9. Product/version metadata in the bundle is sparse, so asset validation should rely on installed plugin evidence.
Mitigation direction
- Inventory WordPress sites using Jupiter X Core and record installed versions.
- Update Jupiter X Core to version 4.6.9 or later where applicable.
- Confirm whether the premium version is activated on each site.
- Do not rely on the 4.6.5 partial patch as complete protection.
- If updating is blocked, follow vendor guidance or disable the affected plugin until remediated.
Validation and detection
- Verify plugin version from WordPress admin, filesystem, or deployment inventory.
- Confirm vulnerable sites have the premium plugin functionality activated.
- Review web logs for unusual unauthenticated file download activity.
- Check whether sensitive configuration files may have been exposed.
- Document fixed versions and retest after update without using offensive payloads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: 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 lookupFile 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 lookupCVE-2023-3813 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f767d94b-fe92-4b69-9d81-96de51e12983?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/jupiterx-core/trunk/includes/extensions/raven/includes/utils.php?rev=2777235#L425CVE reference
- https://plugins.trac.wordpress.org/changeset/3138013/jupiterx-core/trunk/includes/extensions/raven/includes/utils.phpCVE reference
- https://plugins.trac.wordpress.org/changeset/3142669/jupiterx-core/trunk/includes/extensions/raven/includes/utils.phpCVE reference
- https://plugins.trac.wordpress.org/browser/jupiterx-core/tags/4.6.9/includes/extensions/raven/includes/utils.php#L451CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.