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

> Authenticated users can inject arbitrary scripts via specific parameters in Plunet BusinessManager, potentially compromising other users' sessions.

- **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:** No
- **Published:** 23 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rjc8-j2rv-vwfj

## What is CVE-2009-0699?

CVE-2009-0699 is a low-severity cross-site scripting vulnerability in n/a, published on 23 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

Cross-site scripting (XSS) vulnerability in pagesUTF8/auftrag_allgemeinauftrag.jsp in Plunet BusinessManager 4.1 and earlier allows remote authenticated users to inject arbitrary web script or HTML via the (1) QUB and (2) Bez74 parameters.

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

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

It affects 1 product.


Products: Plunet Business Manager.

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

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

## Is CVE-2009-0699 being exploited?

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

Public exploit code:

- Plunet BusinessManager 4.1 - '/pagesUTF8/auftrag_allgemeinauftrag.jsp' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0700](https://insights.sbomify.com/CVE-2009-0700/): Missing authorization in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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