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

> Remote attackers can inject PHP code into Mozzers SubSystem via the add.php script, leading to arbitrary code execution.

- **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 needed
- **Fix available:** No
- **Published:** 22 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mhv3-h4q9-c5v3

## What is CVE-2007-2169?

CVE-2007-2169 is a high-severity code injection vulnerability in n/a, published on 22 Apr 2007. It can be exploited over the network, with no action from the victim.

### Official description

Static code injection vulnerability in add.php in Mozzers SubSystem 1.0 allows remote attackers to inject PHP code into subs.php via the (1) Sub-name or (2) Sub-url field.  NOTE: an earlier report indicated that the add action can be reached through a request to index.php.

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

It affects 1 product.


Products: Mozzers Subsystem Mozzers Subsystem.

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

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

## Is CVE-2007-2169 being exploited?

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

Public exploit code:

- Mozzers SubSystem final - 'subs.php' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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