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

> Remote attackers could execute arbitrary PHP code via a URL in the header parameter, though the vulnerability is disputed and the researcher is unreliable.

- **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:** 17 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-85cj-5x36-chpg

## What is CVE-2007-4383?

CVE-2007-4383 is a medium-severity code injection vulnerability in n/a, published on 17 Aug 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 tracking.php in Trackeur 1 allows remote attackers to execute arbitrary PHP code via a URL in the header parameter.  NOTE: CVE and a third party dispute this vulnerability because header is defined before use.  The researcher is known to be unreliable

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

It affects 1 product.


Products: Trackeur Trackeur.

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

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

## Is CVE-2007-4383 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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