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

> Remote attackers can inject arbitrary web script or HTML into blog posts via multiple parameters, potentially compromising user sessions.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** No
- **Published:** 15 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2v9m-wfhr-4823

## What is CVE-2006-4829?

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

Multiple cross-site scripting (XSS) vulnerabilities in David Czarnecki Blojsom 2.31 allow remote attackers to inject arbitrary web script or HTML via the (1) blog-category-description, (2) blog-entry-title, (3) rss-enclosure-url, (4) technorati-tagsi, or (5) blog-category-name parameter in a blog post.

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

It affects 1 product.


Products: Blojsom Blojsom.

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

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

## Is CVE-2006-4829 being exploited?

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

Public exploit code:

- Blojsom 2.31 - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4830](https://insights.sbomify.com/CVE-2006-4830/): Path traversal in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4829 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4829 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-4829/ (Markdown: https://insights.sbomify.com/CVE-2006-4829/index.md)
```

## Sources

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

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