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

> Remote unauthenticated attackers can delete arbitrary files on the server via directory traversal in Snow Monkey Forms.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 28 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-h734-8jrm-gjjr

## What is CVE-2023-32623?

CVE-2023-32623 is a critical path traversal vulnerability in Snow Monkey Forms, published on 28 Jun 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 v5.1.1 and earlier allows a remote unauthenticated attacker to delete arbitrary files on the server.

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

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

It affects 1 product.


Products: 2inc Snow Monkey Forms.

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

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

## Is CVE-2023-32623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32623 is a critical path traversal vulnerability in Snow Monkey Forms, published on 28 Jun 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-32623 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-32623/ (Markdown: https://insights.sbomify.com/CVE-2023-32623/index.md)
```

## Sources

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

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