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

> Remote attackers can inject arbitrary web script or HTML via the domain parameter in DirectAdmin, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 3 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vh6r-jh59-2pxf

## What is CVE-2006-2153?

CVE-2006-2153 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 May 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

Cross-site scripting (XSS) vulnerability in HTM_PASSWD in DirectAdmin Hosting Management allows remote attackers to inject arbitrary web script or HTML via the domain parameter.

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

It affects 1 product.


Products: Jbmc Software Directadmin.

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

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

## Is CVE-2006-2153 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2153 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 May 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-2153 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-2153/ (Markdown: https://insights.sbomify.com/CVE-2006-2153/index.md)
```

## Sources

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

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