# CVE-2007-5322: Command injection in n/a

> Remote attackers can execute arbitrary programs via the FoxDoCmd function in the Visual FoxPro ActiveX control, requiring user interaction.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f8g8-rvj9-6xc4

## What is CVE-2007-5322?

CVE-2007-5322 is a high-severity command injection vulnerability in n/a, published on 9 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insecure method vulnerability in the FPOLE.OCX 6.0.8450.0 ActiveX control in Microsoft Visual FoxPro 6.0 allows remote attackers to execute arbitrary programs by specifying them as an argument to the FoxDoCmd function.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Microsoft Visual Foxpro.

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

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

## Is CVE-2007-5322 being exploited?

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

Public exploit code:

- Microsoft Visual FoxPro 6.0 - 'FPOLE.OCX' Arbitrary Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0696](https://insights.sbomify.com/CVE-2002-0696/): Security feature bypass in n/a (high 7.5)
- [CVE-2008-0236](https://insights.sbomify.com/CVE-2008-0236/): Command injection in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5322 is a high-severity command injection vulnerability in n/a, published on 9 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5322 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-2007-5322/ (Markdown: https://insights.sbomify.com/CVE-2007-5322/index.md)
```

## Sources

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

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