# CVE-2005-4644: Trac HTML WikiProcessor cross-site scripting (XSS) vulnerability

> Remote attackers can inject arbitrary web script or HTML via IMG tags in Trac, potentially executing code in victim browsers.

- **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:** Yes
- **Published:** 11 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-4644, GHSA-6vhp-hp77-6w52, PYSEC-2005-1

## What is CVE-2005-4644?

CVE-2005-4644 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Jan 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 the HTML WikiProcessor in Edgewall Trac 0.9.2 allows remote attackers to inject arbitrary web script or HTML via javascript in the SRC attribute of an IMG tag.

## Which versions are affected by CVE-2005-4644?

3 open source packages ship an affected version, including trac. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `trac` | PyPI | All versions | 0.10 |
| `trac` | PyPI | All versions | 0.9-stable |
| `trac` | PyPI | All versions | 0.9-stable |

Products: Edgewall Software Trac.

## How do I fix CVE-2005-4644?

Upgrade trac to a fixed version for your release line: 0.10 or 0.9-stable.

## Is CVE-2005-4644 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1406](https://insights.sbomify.com/CVE-2007-1406/): Trac missing Content-Disposition HTTP header (critical 10.0)
- [CVE-2006-5878](https://insights.sbomify.com/CVE-2006-5878/): Edgewall Trac Cross-site request forgery (CSRF) vulnerability (high 7.5)
- [CVE-2005-4065](https://insights.sbomify.com/CVE-2005-4065/): SQL injection in n/a (high 7.5)
- [CVE-2005-3980](https://insights.sbomify.com/CVE-2005-3980/): SQL injection in n/a (high 7.5)
- [CVE-2006-3695](https://insights.sbomify.com/CVE-2006-3695/): Trac reStructuredText breach of privacy and denial of service vulnerability (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4644 and fix it if it is affected.

What it is: CVE-2005-4644 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Jan 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-2005-4644 in the wild and no public exploit code.

Affected packages and fixed versions:
- trac (PyPI): affected all versions; fixed in 0.10
- trac (PyPI): affected all versions; fixed in 0.9-stable
- trac (PyPI): affected all versions; fixed in 0.9-stable

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-2005-4644/ (Markdown: https://insights.sbomify.com/CVE-2005-4644/index.md)
```

## Sources

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

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