dbcve.org
JupiterxWordPress extension · Artbees

CVE-2023-32110

HIGH · 8.8 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 3.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in artbees JupiterX allows PHP Local File Inclusion.This issue affects JupiterX: from n/a through 3.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The JupiterX theme contains a path traversal vulnerability that allows attackers to manipulate file path inputs using '..' sequences to access files outside the intended directory. This improper path limitation enables local file inclusion (LFI), potentially allowing execution of arbitrary PHP files present on the server.

MitigationUpdate JupiterX theme to the latest version which should contain a patch for this path traversal vulnerability. If no update is available, implement strict input validation that rejects path traversal sequences ('..') and restricts file inclusions to expected directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JupiterxWordPress extension
Affected:< 3.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm JupiterX theme installation
    Locate the JupiterX theme directory in your WordPress installation (typically wp-content/themes/jupiterx). Check for a style.css or theme.json file containing the theme version, or query the WordPress database wp_options table for the 'template' or 'stylesheet' value.
    Affected if The JupiterX theme is present in the WordPress themes directory.
  2. Determine installed theme version
    Open the theme's style.css file in the jupiterx directory and read the 'Version:' header, or check the theme version via WordPress admin dashboard under Appearance > Themes.
    Affected if The reported version number is lower than 3.1.0 (e.g., 3.0.x, 2.x.x, etc.).
  3. Identify vulnerable file inclusion functionality
    Search the theme's PHP files for functions that handle file paths for inclusion (such as include, require, include_once, require_once) and accept user-supplied path parameters. Look for code that constructs file paths without proper sanitization.
    Affected if The theme contains PHP files that accept path parameters and use them in file inclusion functions without validating they stay within an allowed directory.
  4. Check for path traversal in HTTP logs
    Review web server access logs (Apache/nginx) and WAF logs for requests to JupiterX-related endpoints containing '../' sequences or URL-encoded equivalents (%2e%2e/). Check for patterns like '?file=../../' or similar.
    Affected if Recent or historical HTTP requests contain '..' traversal sequences targeting JupiterX endpoints.
  5. Inspect for unauthorized file access
    Examine server files for any new or unexpected PHP files in directories outside the expected WordPress structure, particularly in directories writable by the web server.
    Affected if Unexpected PHP files exist outside the standard WordPress directories, or files outside the theme were accessed unexpectedly.

You are affected if the JupiterX theme version is below 3.1.0 and the vulnerable file inclusion functionality exists and is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.0 or later
Fixed in 3.1.0
Interim mitigation

Update JupiterX theme to the latest version which should contain a patch for this path traversal vulnerability. If no update is available, implement strict input validation that rejects path traversal sequences ('..') and restricts file inclusions to expected directories.

Recommended fix Moderate confidence

3.1.0

  1. Backup your WordPress site before making any changes
  2. Update JupiterX theme to version 3.1.0 or later through the WordPress admin dashboard (Appearance > Themes) or via the theme's update mechanism
  3. After updating, verify the version number reflects 3.1.0 or higher in the theme settings
  4. Test critical site functionality to ensure the update did not break existing features
  5. Consider reviewing any custom code or child themes for potential compatibility issues
Caveat Standard theme update - review child theme and custom code compatibility before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jupiterx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32110 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32110 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data