# CVE-2009-4665: CuteSoft CuteEditor Path Traversal vulnerability

> Remote attackers can read arbitrary files via directory traversal in Cute Editor for ASP.NET, exposing sensitive data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w327-wq28-3vmf

## What is CVE-2009-4665?

CVE-2009-4665 is a medium-severity path traversal vulnerability in n/a, published on 5 Mar 2010. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in CuteSoft_Client/CuteEditor/Load.ashx in CuteSoft Components Cute Editor for ASP.NET allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter.

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

## Which versions are affected by CVE-2009-4665?

2 open source packages ship an affected version, including CuteEditor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `CuteEditor` | NuGet | All versions | 6.6 |
| `CuteEditor` | NuGet | All versions | 6.6 |

Products: Cutesoft Components Cute Editor for Asp.net.

## How do I fix CVE-2009-4665?

Upgrade CuteEditor to 6.6 or later.

## Is CVE-2009-4665 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4665 exists.

Public exploit code:

- Cute Editor ASP.NET - Remote File Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4665 and fix it if it is affected.

What it is: CVE-2009-4665 is a medium-severity path traversal vulnerability in n/a, published on 5 Mar 2010. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4665 exists.

Affected packages and fixed versions:
- CuteEditor (NuGet): affected all versions; fixed in 6.6
- CuteEditor (NuGet): affected all versions; fixed in 6.6

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-2009-4665/ (Markdown: https://insights.sbomify.com/CVE-2009-4665/index.md)
```

## Sources

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

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