# CVE-2024-37454: WordPress AWSM Team – Team Showcase Plugin plugin <= 1.3.1 - Local File Inclusion vulnerability

> An attacker can exploit a path traversal vulnerability in the AWSM Team plugin to read arbitrary files from the server.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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-g5xw-fr6p-pc5j

## What is CVE-2024-37454?

CVE-2024-37454 is a medium-severity path traversal vulnerability in AWSM Team, 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 AWSM Innovations AWSM Team allows Path Traversal.This issue affects AWSM Team: from n/a through 1.3.1.

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

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

It affects 1 product.


Products: Awsm Awsm Team.

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

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

## Is CVE-2024-37454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37454 is a medium-severity path traversal vulnerability in AWSM Team, 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-37454 in the wild and no public exploit code.

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

## Sources

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

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