# CVE-2007-5289: Code injection in n/a

> Remote attackers can execute arbitrary code by modifying cached client-side scripts used for workflow logic in HP Mercury Quality Center.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **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:** 24 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9wv3-hv7v-qxrg

## What is CVE-2007-5289?

CVE-2007-5289 is a high-severity code injection vulnerability in n/a, published on 24 Feb 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HP Mercury Quality Center (QC) 9.2 and earlier, and possibly TestDirector, relies on cached client-side scripts to implement "workflow" and decisions about the "capability" of a user, which allows remote attackers to execute arbitrary code via crafted use of the Open Test Architecture (OTA) API, as demonstrated by modifying (1) common.tds, (2) defects.tds, (3) manrun.tds, (4) req.tds, (5) testlab.tds, or (6) testplan.tds in %tmp%\TD_80, and then setting the file's properties to read-only.

Weakness: CWE-264

## Which versions are affected by CVE-2007-5289?

It affects 2 products.


Products: Hp Mercury Quality Center, Hp Testdirector.

## How do I fix CVE-2007-5289?

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

## Is CVE-2007-5289 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1819](https://insights.sbomify.com/CVE-2007-1819/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-1882](https://insights.sbomify.com/CVE-2007-1882/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5289 and fix it if it is affected.

What it is: CVE-2007-5289 is a high-severity code injection vulnerability in n/a, published on 24 Feb 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5289 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-2007-5289/ (Markdown: https://insights.sbomify.com/CVE-2007-5289/index.md)
```

## Sources

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

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