How severe is CVE-2009-4665?

No CVSS score has been assigned to CVE-2009-4665 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-4665?

CVE-2009-4665 affects the following packages: CuteEditor (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2009-4665?

Update CuteEditor to 6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-4665 is resolved across your whole dependency graph.

How do I detect CVE-2009-4665 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CuteEditor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2009-4665 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2009-4665 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2009-4665, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2009-4665?

CVE-2009-4665 has an EPSS (Exploit Prediction Scoring System) score of 6.7%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2009-4665?

CVE-2009-4665 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2009-4665 published, and has it been updated?

CVE-2009-4665 was published on May 2, 2022 and was last updated on February 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

CVE-2009-4665 — CuteEditor

CVE-2009-4665 is a Path Traversal vulnerability in CuteEditor. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for CuteEditor — see the affected versions and patch details below.

CuteSoft CuteEditor Path Traversal vulnerability

Published

May 2, 2022

Updated

Feb 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

.NETCuteEditor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`CuteEditor`	all versions	6.6`dotnet add package CuteEditor --version 6.6`

Affected Products

1 product · 1 configurations

Application

cute editor for asp.netcutesoft_components

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-8785webappsasp✓ Verified

Cute Editor ASP.NET - Remote File Disclosure

by Securitylab.ir · May 26, 2009

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CuteEditor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update CuteEditor to 6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-4665 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2009-4665 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works