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

> Remote attackers can inject arbitrary web script or HTML into Elog log entries, potentially compromising user sessions or data integrity.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** Yes
- **Published:** 28 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gw8f-chrw-2547

## What is CVE-2006-5063?

CVE-2006-5063 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Sep 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 Elog 2.6.1 allows remote attackers to inject arbitrary web script or HTML by editing log entries in HTML mode.

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

It affects 1 product.


Products: Stefan Ritt Elog Web Logbook.

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

Upgrade to a fixed version.

## Is CVE-2006-5063 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5790](https://insights.sbomify.com/CVE-2006-5790/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0597](https://insights.sbomify.com/CVE-2006-0597/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0598](https://insights.sbomify.com/CVE-2006-0598/): Memory corruption in n/a (high 7.5)
- [CVE-2005-0439](https://insights.sbomify.com/CVE-2005-0439/): Memory corruption in n/a (high 7.5)
- [CVE-2005-0440](https://insights.sbomify.com/CVE-2005-0440/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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