Security readout for executives and security teams
Plain-English summary
CVE-2026-3533 affects the Jupiter X Core WordPress plugin through version 4.14.1. A logged-in user with Subscriber-level access could upload unsafe file types through popup template import behavior. Impact ranges from stored cross-site scripting to possible server code execution on configurations that execute .phar files as PHP.
Executive priority
Prioritize remediation for internet-facing WordPress sites with Jupiter X Core, especially where users can self-register. The business risk is high because low-privilege accounts may create stored script risk or, on specific server configurations, code execution.
Technical view
The issue combines missing authorization in import_popup_templates() with insufficient file type validation in upload_files(). It is classified as CWE-434 with CVSS 8.8. The CVE notes dangerous uploads may enable RCE on servers handling .phar as executable PHP, or stored XSS via SVG, DFXP, or XHTML uploads.
Likely exposure
WordPress sites using Jupiter X Core versions up to and including 4.14.1 are potentially exposed, especially if untrusted users can obtain Subscriber accounts. Sites allowing public registration have higher practical exposure.
Exploitation context
The CVE requires authenticated Subscriber-level access or higher, network access, low attack complexity, and no user interaction. There is no provided KEV listing and no cited source here confirming active exploitation.
Researcher notes
Evidence is strongest from the CVE description and Wordfence record. The included WordPress Trac links point to relevant code locations, but this bundle does not include a named fixed version, patch note, or exploitation-in-the-wild confirmation.
Mitigation direction
- Check Artbees/Jupiter X Core vendor guidance and update instructions.
- Upgrade beyond affected versions if a fixed release is available from the vendor.
- Disable or remove Jupiter X Core if it is not required.
- Restrict public user registration and remove unnecessary Subscriber accounts.
- Ensure uploaded files are not executable by the web server.
- Review upload handling for SVG, DFXP, XHTML, and PHAR files.
Validation and detection
- Inventory WordPress sites running Jupiter X Core.
- Confirm installed plugin version is above 4.14.1 or otherwise vendor-cleared.
- Review whether public registration or low-privilege user creation is enabled.
- Check server configuration for executable handling of uploaded PHAR files.
- Inspect upload directories for unexpected SVG, DFXP, XHTML, or PHAR files.
- Review WordPress logs for suspicious authenticated upload activity.
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-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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-2026-3533 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
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/70bc5247-525d-4aae-9d66-efd65c9beee3?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/jupiterx-core/trunk/includes/control-panel-2/includes/class-popup.php?rev=3430169#138CVE reference
- https://plugins.trac.wordpress.org/browser/jupiterx-core/trunk/includes/extensions/raven/includes/modules/forms/fields/file.php?rev=3430169#L214CVE reference
- https://plugins.trac.wordpress.org/browser/jupiterx-core/trunk/includes/extensions/raven/includes/modules/forms/classes/ajax-handler.php?rev=3430169#L434CVE 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.
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.