# CVE-2006-5869: Command injection in n/a

> pstotext allows arbitrary command execution via shell metacharacters in filenames, requiring user interaction to open a malicious file.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1220-1, GHSA-8wrp-qj4q-r6mm

## What is CVE-2006-5869?

CVE-2006-5869 is a medium-severity command injection vulnerability in n/a, published on 26 Nov 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

pstotext before 1.9 allows user-assisted attackers to execute arbitrary commands via shell metacharacters in a file name.

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

It affects 1 product.


Products: Pstotext Pstotext.

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

Upgrade to a fixed version.

## Is CVE-2006-5869 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2536](https://insights.sbomify.com/CVE-2005-2536/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5869 is a medium-severity command injection vulnerability in n/a, published on 26 Nov 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-5869 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-2006-5869/ (Markdown: https://insights.sbomify.com/CVE-2006-5869/index.md)
```

## Sources

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

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