# CVE-2021-37367: Path traversal in n/a

> An attacker can exploit a directory traversal flaw in the admin panel to upload scripts and execute arbitrary commands.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9jxv-v2v3-cmwc

## What is CVE-2021-37367?

CVE-2021-37367 is a high-severity path traversal vulnerability in n/a, published on 10 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CTparental before 4.45.07 is affected by a code execution vulnerability in the CTparental admin panel. Because The file "bl_categories_help.php" is vulnerable to directory traversal, an attacker can create a file that contains scripts and run arbitrary commands.

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

## Which versions are affected by CVE-2021-37367?

It affects 1 product.


Products: Ctparental Project Ctparental.

## How do I fix CVE-2021-37367?

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

## Is CVE-2021-37367 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-37366](https://insights.sbomify.com/CVE-2021-37366/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2021-37365](https://insights.sbomify.com/CVE-2021-37365/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37367 and fix it if it is affected.

What it is: CVE-2021-37367 is a high-severity path traversal vulnerability in n/a, published on 10 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-37367 in the wild and no public exploit code.

Affected product: n/a. 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-2021-37367/ (Markdown: https://insights.sbomify.com/CVE-2021-37367/index.md)
```

## Sources

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

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