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

> Attackers can modify arbitrary variables and potentially execute code via PHP extract function in Apache Stats.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 14 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fg62-m793-pffq

## What is CVE-2007-0930?

CVE-2007-0930 is a high-severity code injection vulnerability in n/a, published on 14 Feb 2007. It can be exploited over the network.

### Official description

Variable extract vulnerability in Apache Stats before 0.0.3beta allows attackers to modify arbitrary variables and conduct attacks via unknown vectors involving the use of PHP's extract function.

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

It affects 1 product.


Products: Apache Stats Apache Stats.

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

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

## Is CVE-2007-0930 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0975](https://insights.sbomify.com/CVE-2007-0975/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0930 is a high-severity code injection vulnerability in n/a, published on 14 Feb 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-0930 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-0930/ (Markdown: https://insights.sbomify.com/CVE-2007-0930/index.md)
```

## Sources

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

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