# CVE-2006-5123: Multiple PHP remote file inclusion vulnerabilities in Albrecht Guenther PHProjekt 5.1.x before 5.1.2 allow remote attackers to execute arbit


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q2wh-2vj3-3rjc

## What is CVE-2006-5123?

CVE-2006-5123 is a high-severity vulnerability in n/a, published on 2 Oct 2006. 

### Official description

Multiple PHP remote file inclusion vulnerabilities in Albrecht Guenther PHProjekt 5.1.x before 5.1.2 allow remote attackers to execute arbitrary PHP code via a URL in the (1) lib_path or (2) lang_path parameter in unspecified files, related to code changes intended to fix inclusion, a different vulnerability than CVE-2002-0451, CVE-2006-4204, and CVE-2006-4609.

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

It affects 1 product.


Products: Phprojekt Phprojekt.

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

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

## Is CVE-2006-5123 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2739](https://insights.sbomify.com/CVE-2004-2739/): Missing authorization in n/a (high 7.5)
- [CVE-2007-1575](https://insights.sbomify.com/CVE-2007-1575/): SQL injection in n/a (high 7.5)
- [CVE-2006-4204](https://insights.sbomify.com/CVE-2006-4204/): Code injection in n/a (high 7.5)
- [CVE-2002-1757](https://insights.sbomify.com/CVE-2002-1757/): Auth bypass in n/a (high 7.5)
- [CVE-2002-1760](https://insights.sbomify.com/CVE-2002-1760/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5123 is a high-severity vulnerability in n/a, published on 2 Oct 2006. 
Exploitation: There is no known exploitation of CVE-2006-5123 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-2006-5123/ (Markdown: https://insights.sbomify.com/CVE-2006-5123/index.md)
```

## Sources

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

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