# CVE-2006-6771: File upload in n/a

> Remote attackers can execute arbitrary PHP code via URL parameters in Irokez CMS when register_globals is enabled.

- **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:** 27 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8263-5wg2-7cg5

## What is CVE-2006-6771?

CVE-2006-6771 is a medium-severity vulnerability in n/a, published on 27 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file inclusion vulnerabilities in Irokez CMS 0.7.1 and earlier, when register_globals is enabled, allow remote attackers to execute arbitrary PHP code via a URL in the (1) GLOBALS[PTH][func] parameter in (a) scripts/gallery.scr.php; the (2) GLOBALS[PTH][spaw] parameter in (b) scripts/xtextarea.scr.php; and the (3) GLOBALS[PTH][classes] parameter in (c) sitemap.scr.php, (d) news.scr.php, (e) polls.scr.php, (f) rss.scr.php, (g) search.scr.php in scripts/, and (h) form.fun.php, (i) general.func.php, (j) groups.func.php, (k) js.func.php, (l) sections.func.php, and (m) users.func.php in functions/.

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

It affects 1 product.


Products: Irokez Irokez Cms.

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

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

## Is CVE-2006-6771 being exploited?

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

Public exploit code:

- Irokez Blog 0.7.1 - Multiple Remote File Inclusions (exploitdb)
- Irokez Blog 0.7.3.2 - Multiple Input Validation Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-4982](https://insights.sbomify.com/CVE-2009-4982/): SQL injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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