# CVE-2002-0266: Information disclosure in n/a

> Remote attackers can obtain the full web root path via error messages from Thunderstone Texis CGI scripts when requesting nonexistent files.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wrh6-2vcx-6fcm

## What is CVE-2002-0266?

CVE-2002-0266 is a medium-severity vulnerability in n/a, published on 3 May 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Thunderstone Texis CGI script allows remote attackers to obtain the full path of the web root via a request for a nonexistent file, which generates an error message that includes the full pathname.

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

It affects 1 product.


Products: Thunderstone Software Texis.

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

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

## Is CVE-2002-0266 being exploited?

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

Public exploit code:

- Thunderstone TEXIS 3.0 - Full Path Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0266 is a medium-severity vulnerability in n/a, published on 3 May 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0266 exists.

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

## Sources

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

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