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

> Authenticated users can inject scripts into DirectAdmin, potentially stealing sessions or modifying data.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** 20 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p77v-j929-9938

## What is CVE-2006-5983?

CVE-2006-5983 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Nov 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 JBMC Software DirectAdmin 1.28.1 allow remote authenticated users to inject arbitrary web script or HTML via the (1) user parameter to (a) CMD_SHOW_RESELLER or (b) CMD_SHOW_USER in the Admin level; the (2) TYPE parameter to (c) CMD_TICKET_CREATE or (d) CMD_TICKET, the (3) user parameter to (e) CMD_EMAIL_FORWARDER_MODIFY, (f) CMD_EMAIL_VACATION_MODIFY, or (g) CMD_FTP_SHOW, and the (4) name parameter to (h) CMD_EMAIL_LIST in the User level; or the (5) user parameter to (i) CMD_SHOW_USER in the Reseller level.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Directadmin Directadmin.

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

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

## Is CVE-2006-5983 being exploited?

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

Public exploit code:

- DirectAdmin 1.28/1.29 - 'CMD_SHOW_RESELLER' Cross-Site Scripting (exploitdb)
- DirectAdmin 1.28/1.29 - 'CMD_SHOW_USER' Cross-Site Scripting (exploitdb)
- DirectAdmin 1.28/1.29 - 'CMD_TICKET_CREATE' Cross-Site Scripting (exploitdb)
- DirectAdmin 1.28/1.29 - 'CMD_EMAIL_FORWARDER_MODIFY' Cross-Site Scripting (exploitdb)
- DirectAdmin 1.28/1.29 - 'CMD_TICKET' Cross-Site Scripting (exploitdb)
- DirectAdmin 1.28/1.29 - 'CMD_EMAIL_VACATION_MODIFY' Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-18045](https://insights.sbomify.com/CVE-2017-18045/): Denial of service in n/a (critical 9.8)
- [CVE-2019-9625](https://insights.sbomify.com/CVE-2019-9625/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2009-1525](https://insights.sbomify.com/CVE-2009-1525/): Command injection in n/a (high 8.5)
- [CVE-2025-56551](https://insights.sbomify.com/CVE-2025-56551/): Cross-site scripting in n/a (high 8.2)
- [CVE-2009-1526](https://insights.sbomify.com/CVE-2009-1526/): Path traversal in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5983 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Nov 2006. Any signed-in user can exploit it over the network, 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-5983 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-5983/ (Markdown: https://insights.sbomify.com/CVE-2006-5983/index.md)
```

## Sources

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

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