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

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in Leadhound affiliate pages, requiring user interaction to execute.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-39jw-8769-j5wh

## What is CVE-2006-2063?

CVE-2006-2063 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Leadhound Full and LITE 2.1, and probably the Network Version "Full Version", allow remote attackers to inject arbitrary web script or HTML via the login parameter in (1) agent_affil.pl, (2) agent_help.pl, (3) agent_faq.pl, (4) agent_help_insert.pl, (5) sign_out.pl, (6) members.pl, (7) modify_agent_1.pl, (8) modify_agent_2.pl, (9) modify_agent.pl, (10) agent_links.pl, (11) agent_stats_pending_leads.pl, (12) agent_logoff.pl, (13) agent_rev_det.pl, (14) agent_subaffiliates.pl, (15) agent_stats_pending_leads.pl, (16) agent_transactions.pl, (17) agent_payment_history.pl, (18) agent_summary.pl, (19) agent_camp_all.pl, (20) agent_camp_new.pl, (21) agent_camp_notsub.pl, (22) agent_campaign.pl, (23) agent_camp_expired.pl, (24) agent_stats_det.pl, (25) agent_stats.pl, (26) agent_camp_det.pl, (27) agent_camp_sub.pl, (28) agent_affil_list.pl, and (29) agent_affil_code.pl; the logged parameter in (30) agent_faq.pl, (31) agent_help_insert.pl, (32) members.pl, (33) modify_agent_1.pl, (34) modify_agent_2.pl, (35) modify_agent.pl, (36) agent_links.pl, (37) agent_subaffiliates.pl, (38) agent_stats_pending_leads.pl, (39) agent_transactions.pl, (40) agent_summary.pl, (41) agent_camp_all.pl, (42) agent_camp_new.pl, (43) agent_camp_notsub.pl, (44) agent_campaign.pl, (45) agent_camp_expired.pl, (46) agent_stats.pl, (47) agent_camp_det.pl, (48) agent_camp_sub.pl, (49) agent_affil_list.pl, and (50) agent_affil_code.pl; the camp_id parameter in (51) agent_links.pl, (52) agent_subaffiliates.pl, and (53) agent_camp_det.pl; the (54) banner parameter in agent_links.pl; the offset parameter in (55) agent_links.pl, (56) agent_subaffiliates.pl, (57) agent_transactions.pl, and (58) agent_summary.pl; the date parameter in (59) agent_subaffiliates.pl, (60) agent_transactions.pl, and (61) agent_summary.pl; the dates parameter in (62) agent_rev_det.pl and (63) agent_stats_det.pl; the (64) page parameter in agent_camp_det.pl; the (65) agent_id parameter in agent_commission_statement.pl; and the (66) lost password field in lost_pwd.pl.

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

It affects 2 products.


Products: Leadhound Network Leadhound Full, Leadhound Network Leadhound Lite.

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

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

## Is CVE-2006-2063 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2062](https://insights.sbomify.com/CVE-2006-2062/): SQL injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2063 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-2063 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-2063/ (Markdown: https://insights.sbomify.com/CVE-2006-2063/index.md)
```

## Sources

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

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