# CVE-2002-2413: WebSite Pro 3.1.11.0 on Windows allows remote attackers to read script source code for files with extensions greater than 3 characters via a


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r54v-wfmq-86f6

## What is CVE-2002-2413?

CVE-2002-2413 is a medium-severity vulnerability in n/a, published on 1 Nov 2007. 

### Official description

WebSite Pro 3.1.11.0 on Windows allows remote attackers to read script source code for files with extensions greater than 3 characters via a URL request that uses the equivalent 8.3 file name.

## Which versions are affected by CVE-2002-2413?

It affects 1 product.


Products: Deerfield Website Pro.

## How do I fix CVE-2002-2413?

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

## Is CVE-2002-2413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2413 and fix it if it is affected.

What it is: CVE-2002-2413 is a medium-severity vulnerability in n/a, published on 1 Nov 2007. 
Exploitation: There is no known exploitation of CVE-2002-2413 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-2002-2413/ (Markdown: https://insights.sbomify.com/CVE-2002-2413/index.md)
```

## Sources

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

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