# CVE-2024-33557: WordPress XStore Core plugin <= 5.3.8 - Local File Inclusion vulnerability

> Attackers can exploit a path traversal flaw in the XStore Core plugin to include arbitrary local files, potentially leading to code execution or data disclosure.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-qfjr-gjmj-rcfj

## What is CVE-2024-33557?

CVE-2024-33557 is a high-severity path traversal vulnerability in 8theme XStore Core, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in 8theme XStore Core allows PHP Local File Inclusion.This issue affects XStore Core: from n/a through 5.3.8.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-33557?

It affects 1 product.


Products: 8theme Xstore Core.

## How do I fix CVE-2024-33557?

No fix has been published for CVE-2024-33557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-33557 being exploited?

There is no known exploitation of CVE-2024-33557 in the wild and no public exploit code.

## Other vulnerabilities in 8theme XStore Core

- [CVE-2024-33552](https://insights.sbomify.com/CVE-2024-33552/): WordPress XStore Core plugin <= 5.3.8 - Unauthenticated Account Takeover vulnerability (critical 9.8)
- [CVE-2024-33551](https://insights.sbomify.com/CVE-2024-33551/): WordPress XStore Core plugin <= 5.3.5 - Unauthenticated SQL Injection vulnerability (critical 9.3)
- [CVE-2024-33553](https://insights.sbomify.com/CVE-2024-33553/): WordPress XStore Core plugin <= 5.3.5 - Unauthenticated PHP Object Injection vulnerability (critical 9.0)
- [CVE-2024-33556](https://insights.sbomify.com/CVE-2024-33556/): WordPress XStore Core plugin <= 5.3.8 - Limited Arbitrary File Upload vulnerability (high 8.2)
- [CVE-2024-33555](https://insights.sbomify.com/CVE-2024-33555/): WordPress XStore Core plugin <= 5.3.8 - Multiple Authenticated Broken Access Control vulnerability (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33557 and fix it if it is affected.

What it is: CVE-2024-33557 is a high-severity path traversal vulnerability in 8theme XStore Core, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33557 in the wild and no public exploit code.

Affected product: 8theme XStore Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-33557/ (Markdown: https://insights.sbomify.com/CVE-2024-33557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-33557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-33557
- OSV: https://osv.dev/vulnerability/CVE-2024-33557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-33557/
Summaries are generated and may contain mistakes; the official description above is the record.