# CVE-2005-0650: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple input fields in ProjectBB, potentially stealing user data or hijacking accounts.

- **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:** 4 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qpqf-xrcv-47ch

## What is CVE-2005-0650?

CVE-2005-0650 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Mar 2005. 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 ProjectBB 0.4.5.1 allow remote attackers to inject arbitrary web script or HTML via (1) the pages parameter to divers.php (incorrectly referred to as "drivers.php" by some sources), (2) in the search feature text area, (3) forum name, (4) site name or (5) the maximum avatar size in the option section, (5) new category or (6) new forum fields in the forum section.

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

It affects 1 product.


Products: Projectbb Projectbb.

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

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

## Is CVE-2005-0650 being exploited?

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

Public exploit code:

- ProjectBB 0.4.5.1 - Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0651](https://insights.sbomify.com/CVE-2005-0651/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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