# CVE-2009-0359: Cross-site scripting in n/a

> Authenticated users can inject arbitrary scripts via message titles or names, enabling session hijacking or content manipulation in Samizdat.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** 17 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0359, DTSA-194-1, GHSA-hj2w-cqp4-v4p9

## What is CVE-2009-0359?

CVE-2009-0359 is a low-severity cross-site scripting vulnerability in n/a, published on 17 Feb 2009. 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 Samizdat before 0.6.2 allow remote authenticated users to inject arbitrary web script or HTML via the (1) message title or (2) user full name.

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

## Which versions are affected by CVE-2009-0359?

It affects 1 product.


Products: Nongnu Samizdat.

## How do I fix CVE-2009-0359?

Upgrade to a fixed version.

## Is CVE-2009-0359 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0359 and fix it if it is affected.

What it is: CVE-2009-0359 is a low-severity cross-site scripting vulnerability in n/a, published on 17 Feb 2009. 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-2009-0359 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-2009-0359/ (Markdown: https://insights.sbomify.com/CVE-2009-0359/index.md)
```

## Sources

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

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