# CVE-2007-4088: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in Vikingboard, potentially compromising user sessions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p537-w4qf-x2cx

## What is CVE-2007-4088?

CVE-2007-4088 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Jul 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Vikingboard 0.1.2 allow remote attackers to inject arbitrary web script or HTML via the (1) id, (2) f, (3) quote, and (4) act parameters to cp.php; the (5) u parameter to user.php; the (6) f parameter to post.php; the (7) s parameter to topic.php; the (8) quote, (9) t, (10) poll, and (11) p parameters to post.php; the (12) Message Title field of a private message (PM) in mode 6 of cp.php; the (13) title field of a private message (PM) in mode 7 of cp.php; and (14) allow user-assisted remote attackers to inject arbitrary web script or HTML via a dosearch action to search.php, which reflects the first lines of all posts by a user.  NOTE: the act parameter to help.php and the p parameter to report.php are already covered by CVE-2006-4708.  NOTE: vectors 12 and 13 might overlap CVE-2006-6283.1.  NOTE: vector 14 might overlap CVE-2006-4708.b.

## Which versions are affected by CVE-2007-4088?

It affects 1 product.


Products: Vikingboard Vikingboard.

## How do I fix CVE-2007-4088?

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

## Is CVE-2007-4088 being exploited?

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

Public exploit code:

- Vikingboard 0.1.2 - 'cp.php' Cross-Site Scripting (exploitdb)
- Vikingboard 0.1.2 - 'user.php' Cross-Site Scripting (exploitdb)
- Vikingboard 0.1.2 - 'post.php' Cross-Site Scripting (exploitdb)
- Vikingboard 0.1.2 - 'topic.php' Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6282](https://insights.sbomify.com/CVE-2006-6282/): Information disclosure in n/a (critical 9.3)
- [CVE-2006-6284](https://insights.sbomify.com/CVE-2006-6284/): Path traversal in n/a (critical 9.0)
- [CVE-2006-4708](https://insights.sbomify.com/CVE-2006-4708/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-4709](https://insights.sbomify.com/CVE-2006-4709/): SQL injection in n/a (medium 5.0)
- [CVE-2007-4089](https://insights.sbomify.com/CVE-2007-4089/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4088 and fix it if it is affected.

What it is: CVE-2007-4088 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Jul 2007. An attacker can exploit it over the internet without logging in, 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-2007-4088 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-2007-4088/ (Markdown: https://insights.sbomify.com/CVE-2007-4088/index.md)
```

## Sources

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

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