# CVE-2024-37268: WordPress Striking theme <= 2.3.4 - Local File Inclusion vulnerability

> Attackers can exploit a path traversal flaw in the Striking WordPress theme to read arbitrary files from the server.

- **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:** 9 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-w54w-cwh9-m6xv

## What is CVE-2024-37268?

CVE-2024-37268 is a high-severity path traversal vulnerability in kaptinlin Striking, published on 9 Jul 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 kaptinlin Striking allows Path Traversal.This issue affects Striking: from n/a through 2.3.4.

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

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

It affects 1 product.


Products: Kaptinlin Striking.

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

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

## Is CVE-2024-37268 being exploited?

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

## Other vulnerabilities in kaptinlin Striking

- [CVE-2024-37267](https://insights.sbomify.com/CVE-2024-37267/): WordPress Striking theme <= 2.3.4 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37268 is a high-severity path traversal vulnerability in kaptinlin Striking, published on 9 Jul 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-37268 in the wild and no public exploit code.

Affected product: kaptinlin Striking. 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-37268/ (Markdown: https://insights.sbomify.com/CVE-2024-37268/index.md)
```

## Sources

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

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