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

> Authenticated attackers can delete arbitrary files on the server via directory traversal in Pulse CMS.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hx32-4339-g7jh

## What is CVE-2010-0989?

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

### Official description

Directory traversal vulnerability in delete.php in Pulse CMS before 1.2.3 allows remote authenticated users to delete arbitrary files via directory traversal sequences in the f parameter.

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

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

It affects 1 product.


Products: Pulsecms Pulse Cms.

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

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

## Is CVE-2010-0989 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4330](https://insights.sbomify.com/CVE-2010-4330/): Path traversal in n/a (medium 6.8)
- [CVE-2010-0992](https://insights.sbomify.com/CVE-2010-0992/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2010-0993](https://insights.sbomify.com/CVE-2010-0993/): File upload in n/a (medium 6.0)
- [CVE-2010-1334](https://insights.sbomify.com/CVE-2010-1334/): File upload in n/a (medium 6.0)
- [CVE-2010-0988](https://insights.sbomify.com/CVE-2010-0988/): Code injection in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0989 is a medium-severity path traversal vulnerability in n/a, published on 26 Mar 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0989 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-2010-0989/ (Markdown: https://insights.sbomify.com/CVE-2010-0989/index.md)
```

## Sources

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

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