# CVE-2007-0975: Other in n/a

> Attackers can overwrite critical variables in Apache Stats via variable extraction, potentially leading to undefined impacts.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-488g-qcwc-pg32

## What is CVE-2007-0975?

CVE-2007-0975 is a medium-severity vulnerability in n/a, published on 16 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Variable extraction vulnerability in Ian Bezanson Apache Stats before 0.0.3 beta allows attackers to overwrite critical variables, with unknown impact, when the extract function is used on the _REQUEST superglobal array.

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

It affects 1 product.


Products: Apache Stats Apache Stats.

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

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

## Is CVE-2007-0975 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0930](https://insights.sbomify.com/CVE-2007-0930/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0975 is a medium-severity vulnerability in n/a, published on 16 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0975 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-0975/ (Markdown: https://insights.sbomify.com/CVE-2007-0975/index.md)
```

## Sources

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

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