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

> Remote attackers can execute arbitrary commands via file inclusion if register_globals is enabled in dotProject.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2006
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-7x4q-26xj-gjr7

## What is CVE-2006-0755?

CVE-2006-0755 is a medium-severity code injection vulnerability in n/a, published on 18 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file include vulnerabilities in dotProject 2.0.1 and earlier, when register_globals is enabled, allow remote attackers to execute arbitrary commands via the baseDir parameter in (1) db_adodb.php, (2) db_connect.php, (3) session.php, (4) vw_usr_roles.php, (5) calendar.php, (6) date_format.php, and (7) tasks/gantt.php; and the dPconfig[root_dir] parameter in (8) projects/gantt.php, (9) gantt2.php, and (10) vw_files.php.  NOTE: the vendor disputes this issue, stating that the product documentation clearly recommends that the system administrator disable register_globals, and that the check.php script warns against this setting.  Also, the vendor says that the protection.php/siteurl vector is incorrect because protection.php does not exist in the product

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

It affects 1 product.


Products: Dotproject Dotproject.

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

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

## Is CVE-2006-0755 being exploited?

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

Public exploit code:

- dotProject 2.0 - '/modules/projects/gantt.php?dPconfig[root_dir]' Remote File Inclusion (exploitdb)
- dotProject 2.0 - '/includes/db_connect.php?baseDir' Remote File Inclusion (exploitdb)
- dotProject 2.0 - '/includes/session.php?baseDir' Remote File Inclusion (exploitdb)
- dotProject 2.0 - '/modules/projects/gantt2.php?dPconfig[root_dir]' Remote File Inclusion (exploitdb)
- dotProject 2.0 - '/modules/projects/vw_files.php?dPconfig[root_dir]' Remote File Inclusion (exploitdb)
- dotProject 2.0 - '/modules/admin/vw_usr_roles.php?baseDir' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1428](https://insights.sbomify.com/CVE-2002-1428/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-4234](https://insights.sbomify.com/CVE-2006-4234/): Code injection in n/a (high 7.5)
- [CVE-2012-5701](https://insights.sbomify.com/CVE-2012-5701/): SQL injection in n/a (medium 6.8)
- [CVE-2008-6747](https://insights.sbomify.com/CVE-2008-6747/): Missing authorization in n/a (medium 6.8)
- [CVE-2007-5486](https://insights.sbomify.com/CVE-2007-5486/): Missing authorization in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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