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

> Remote attackers can inject PHP code into configuration files via the number parameter, leading to arbitrary code execution on the server.

- **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:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5q5m-mjqc-gj8w

## What is CVE-2007-2167?

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

### Official description

Static code injection vulnerability in process.php in AimStats 3.2 allows remote attackers to inject PHP code into config.php via the number parameter in an update action.

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

It affects 1 product.


Products: Aimstats Aimstats.

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

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

## Is CVE-2007-2167 being exploited?

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

Public exploit code:

- AimStats 3.2 - 'process.php?update' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2167 is a high-severity code injection vulnerability in n/a, published on 22 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2167 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-2167/ (Markdown: https://insights.sbomify.com/CVE-2007-2167/index.md)
```

## Sources

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

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