# CVE-2006-1120: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in DCP-Portal when register_globals is enabled.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9jcq-wqvg-vp8r

## What is CVE-2006-1120?

CVE-2006-1120 is a low-severity cross-site scripting vulnerability in n/a, published on 9 Mar 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in DCP-Portal 6.1.1 and earlier, with register_globals enabled, allow remote attackers to inject arbitrary web script or HTML via the (1) its_url parameter in the documents page and (2) url parameter in the send_write page of (a) index.php; (3) subject, and (4) images parameters to (b) calendar.php; (5) bid, (6) replying_msg, (7) subject, (8) body, and (9) mid parameters to (c) forums.php; (10) subject and (11) message parameters to (d) inbox.php; (12) subject_color and (13) email parameters to (e) lostpassword.php; and the (14) c_name, (15) content_inicial, and (16) cid parameters to (f) mycontents.php.  NOTE: the calendar.php/day vector is already subsumed by CVE-2006-0220, and the calendar.php/month, calendar.php/year, and search.php/q parameters for calendar.php are already subsumed by CVE-2004-2511.

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

It affects 1 product.


Products: Codeworx Technologies Dcp-Portal.

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

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

## Is CVE-2006-1120 being exploited?

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

Public exploit code:

- DCP-Portal 3.7/4.x/5.x/6.x - 'index.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- DCP-Portal 3.7/4.x/5.x/6.x - 'calendar.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- DCP-Portal 3.7/4.x/5.x/6.x - 'forums.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- DCP-Portal 3.7/4.x/5.x/6.x - 'inbox.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- DCP-Portal 3.7/4.x/5.x/6.x - 'lostpassword.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- DCP-Portal 3.7/4.x/5.x/6.x - 'mycontents.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4837](https://insights.sbomify.com/CVE-2006-4837/): Code injection in n/a (high 7.5)
- [CVE-2005-4227](https://insights.sbomify.com/CVE-2005-4227/): SQL injection in n/a (high 7.5)
- [CVE-2005-3365](https://insights.sbomify.com/CVE-2005-3365/): SQL injection in n/a (high 7.5)
- [CVE-2005-0454](https://insights.sbomify.com/CVE-2005-0454/): SQL injection in n/a (high 7.5)
- [CVE-2006-4836](https://insights.sbomify.com/CVE-2006-4836/): SQL injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1120 is a low-severity cross-site scripting vulnerability in n/a, published on 9 Mar 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1120 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-1120/ (Markdown: https://insights.sbomify.com/CVE-2006-1120/index.md)
```

## Sources

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

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