Safeguard
Vulnerability Analysis•

CVE-2023-32110: High Local File Inclusion in JupiterX Theme

CVE-2023-32110 is a high (CVSS 7.6) local file inclusion flaw in the JupiterX WordPress theme up to 3.0.0. Update to 3.1.0 or later, per Patchstack.

Safeguard Security Team
3 min read

CVE-2023-32110 is a high severity path traversal flaw, scored 7.6, in the JupiterX WordPress theme from artbees. It allows PHP local file inclusion in versions through 3.0.0, and a Subscriber account is enough. Patchstack lists 3.1.0 as the patched version, so update to 3.1.0 or later.

What's affected

The NVD record, dated 2024-05-17, describes improper limitation of a pathname to a restricted directory (CWE-22) in artbees JupiterX that allows PHP local file inclusion. It affects versions from n/a through 3.0.0. The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L.

The Patchstack entry cited by the record says the same: 3.0.0 and earlier are vulnerable and 3.1.0 is the patched version. It adds that the privilege needed is Subscriber, the lowest logged in role on a typical WordPress site, and that the flaw is a Local File Inclusion. Patchstack rates it high priority and says flaws like this are used in mass exploitation campaigns, but it does not say this specific flaw has been exploited. The CVE is not in the CISA Known Exploited Vulnerabilities catalog, so no source we fetched reports active use.

The two sources agree on the score and the affected range.

How to check if you're exposed

Check the installed theme version with WP-CLI:

wp theme get jupiterx --field=version

If the theme is not installed the command fails. Otherwise compare the result with 3.1.0. You can also open Appearance, then Themes, and look at the theme details. Child themes inherit the parent theme code, so check the parent even when a child theme is active.

Because the flaw needs only a Subscriber account, look at how registration works on each site. A site that lets anyone sign up gives an attacker that role for free. Review user lists for accounts you do not recognize.

What to do now

  1. Update JupiterX to 3.1.0 or later on every site, including staging.
  2. If you cannot update immediately, close open user registration or reduce the default role until you can.
  3. Review recent Subscriber accounts and remove ones that look automated.
  4. Check web server logs for unusual requests that carry path style values in parameters.
  5. Keep configuration files such as wp-config.php out of reach of web users by restricting file permissions, and rotate secrets if you suspect exposure.

Why it matters

CWE-22 lets a request steer a file path outside the folder it was meant to read. In PHP, a path that is passed to an include call can load a file as code. This is what turns a path problem into a code execution problem on a server. At the least, files such as configuration data can leak, and the vector rates confidentiality impact as high.

The low privilege and the lack of user interaction make this easier to reach than a flaw that needs an administrator. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect installed desktop applications, so those need a manual inventory.

Quick check

Does the attacker need to be an admin?

No. Patchstack says a Subscriber account is enough.

Which version fixes it?

Patchstack lists 3.1.0 as the patched version. Update to 3.1.0 or later.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.