# CVE-2005-2793: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in phpLDAPadmin via the custom_welcome_page parameter in welcome.php.

- **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:** Yes
- **Published:** 2 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2793, GHSA-48jv-v9q6-gcg3

## What is CVE-2005-2793?

CVE-2005-2793 is a high-severity code injection vulnerability in n/a, published on 2 Sep 2005. 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 welcome.php in phpLDAPadmin 0.9.6 and 0.9.7 allows remote attackers to execute arbitrary PHP code via the custom_welcome_page parameter.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2005-2793?

It affects 1 product.


Products: Phpldapadmin Project Phpldapadmin.

## How do I fix CVE-2005-2793?

Upgrade to a fixed version.

## Is CVE-2005-2793 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12689](https://insights.sbomify.com/CVE-2018-12689/): Other in n/a (critical 9.8)
- [CVE-2011-4075](https://insights.sbomify.com/CVE-2011-4075/): Code injection in n/a (high 7.5)
- [CVE-2009-4427](https://insights.sbomify.com/CVE-2009-4427/): Path traversal in n/a (high 7.5)
- [CVE-2005-2654](https://insights.sbomify.com/CVE-2005-2654/): Auth bypass in n/a (high 7.5)
- [CVE-2005-2792](https://insights.sbomify.com/CVE-2005-2792/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2793 and fix it if it is affected.

What it is: CVE-2005-2793 is a high-severity code injection vulnerability in n/a, published on 2 Sep 2005. 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-2005-2793 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-2005-2793/ (Markdown: https://insights.sbomify.com/CVE-2005-2793/index.md)
```

## Sources

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

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