# CVE-2023-28413: Path traversal in Snow Monkey Forms

> Remote unauthenticated attackers can exploit a directory traversal flaw to read sensitive data, modify the site, or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-h2cx-cfgv-2g8f

## What is CVE-2023-28413?

CVE-2023-28413 is a critical path traversal vulnerability in Snow Monkey Forms, published on 23 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Snow Monkey Forms versions v5.0.6 and earlier allows a remote unauthenticated attacker to obtain sensitive information, alter the website, or cause a denial-of-service (DoS) condition.

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

## Which versions are affected by CVE-2023-28413?

It affects 1 product.


Products: Snow Monkey Forms Project Snow Monkey Forms.

## How do I fix CVE-2023-28413?

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

## Is CVE-2023-28413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28413 and fix it if it is affected.

What it is: CVE-2023-28413 is a critical path traversal vulnerability in Snow Monkey Forms, published on 23 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28413 in the wild and no public exploit code.

Affected product: Snow Monkey Forms. 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-2023-28413/ (Markdown: https://insights.sbomify.com/CVE-2023-28413/index.md)
```

## Sources

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

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