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

> Remote attackers can execute arbitrary PHP code via a URL parameter in stat12, though the report is considered likely invalid.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ff9v-6g5g-75gj

## What is CVE-2007-1967?

CVE-2007-1967 is a medium-severity code injection vulnerability in n/a, published on 11 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in index.php in stat12 allows remote attackers to execute arbitrary PHP code via a URL in the langpath parameter.  NOTE: this issue was published by an unreliable researcher, and there is little information to determine which product is actually affected.  This is probably an invalid report based on analysis by CVE and a third party

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

It affects 1 product.


Products: Stat12 Stat12.

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

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

## Is CVE-2007-1967 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1967 is a medium-severity code injection vulnerability in n/a, published on 11 Apr 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-1967 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-1967/ (Markdown: https://insights.sbomify.com/CVE-2007-1967/index.md)
```

## Sources

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

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