# CVE-2006-4115: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in PgMarket via the CFG[libdir] parameter when register_globals is enabled.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 14 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mrff-8xrf-w772

## What is CVE-2006-4115?

CVE-2006-4115 is a medium-severity code injection vulnerability in n/a, published on 14 Aug 2006. 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 common.inc.php in PgMarket 2.2.3, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via the CFG[libdir] parameter.

## Which versions are affected by CVE-2006-4115?

It affects 1 product.


Products: E-Zest Solutions Pgmarket.

## How do I fix CVE-2006-4115?

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

## Is CVE-2006-4115 being exploited?

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

Public exploit code:

- PgMarket 2.2.3 - 'CFG[libdir]' Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4115 and fix it if it is affected.

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

## Sources

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

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