# CVE-2010-2006: Path traversal in n/a

> Authenticated attackers can exploit a directory traversal flaw in LetoDMS to include and execute arbitrary local files via the lang parameter.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-2146-1, GHSA-7c42-8pjf-wmc2

## What is CVE-2010-2006?

CVE-2010-2006 is a medium-severity path traversal vulnerability in n/a, published on 20 May 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in op/op.Login.php in LetoDMS (formerly MyDMS) 1.7.2 and earlier allows remote authenticated users to include and execute arbitrary local files via a .. (dot dot) in the lang parameter.

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

## Which versions are affected by CVE-2010-2006?

It affects 1 product.


Products: Letodms Letodms.

## How do I fix CVE-2010-2006?

Upgrade to a fixed version.

## Is CVE-2010-2006 being exploited?

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

Public exploit code:

- LetoDms 1.4.x - 'lang' Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-2007](https://insights.sbomify.com/CVE-2010-2007/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2006 and fix it if it is affected.

What it is: CVE-2010-2006 is a medium-severity path traversal vulnerability in n/a, published on 20 May 2010. Any signed-in user can exploit it 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-2010-2006 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-2010-2006/ (Markdown: https://insights.sbomify.com/CVE-2010-2006/index.md)
```

## Sources

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

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