# CVE-2002-1460: Path traversal in n/a

> Remote attackers can read arbitrary files by manipulating upload variables in L-Forum, exposing sensitive data without authentication.

- **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:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p5qv-9mw7-6h8h

## What is CVE-2002-1460?

CVE-2002-1460 is a medium-severity path traversal vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

L-Forum 2.40 and earlier does not properly verify whether a file was uploaded or if the associated variables were set by POST (attachment, attachment_name, attachment_size and attachment_type), which allows remote attackers to read arbitrary files.

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

It affects 1 product.


Products: Leszek Krupinski L-Forum.

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

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

## Is CVE-2002-1460 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1457](https://insights.sbomify.com/CVE-2002-1457/): SQL injection in n/a (high 7.5)
- [CVE-2002-1458](https://insights.sbomify.com/CVE-2002-1458/): Cross-site scripting in n/a (high 7.5)
- [CVE-2002-1459](https://insights.sbomify.com/CVE-2002-1459/): Cross-site scripting in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1460 is a medium-severity path traversal vulnerability in n/a, published on 18 Mar 2003. 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-2002-1460 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-1460/ (Markdown: https://insights.sbomify.com/CVE-2002-1460/index.md)
```

## Sources

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

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