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

> Remote attackers can inject arbitrary web script via crafted BBcode tags in PyForum, requiring victim interaction to execute.

- **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:** No
- **Published:** 23 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p27c-q9wc-vp8q

## What is CVE-2009-4408?

CVE-2009-4408 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Dec 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 models.parser in PyForum 1.0.3 and possibly earlier versions, and possibly zForum, allow remote attackers to inject arbitrary web script or HTML via crafted BBcode (1) img or (2) url tags, which are not properly handled when a post is viewed.

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

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

It affects 1 product.


Products: Pyforum Pyforum.

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

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

## Is CVE-2009-4408 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4407](https://insights.sbomify.com/CVE-2009-4407/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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