# CVE-2004-2352: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via unsanitized cookies in GBook for PHP-Nuke, potentially leading to session hijacking or code execution.

- **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:** 16 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x6wc-272q-h8cg

## What is CVE-2004-2352?

CVE-2004-2352 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Aug 2005. 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

Cross-site scripting (XSS) vulnerability in GBook for PHP-Nuke 1.0 allows remote attackers to inject arbitrary web script or HTML via cookies that are stored in the $_COOKIE PHP variable, which is not cleansed by PHP-Nuke.

## Which versions are affected by CVE-2004-2352?

It affects 1 product.


Products: Martin Bauer Gbook.

## How do I fix CVE-2004-2352?

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

## Is CVE-2004-2352 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1560](https://insights.sbomify.com/CVE-2002-1560/): Auth bypass in n/a (critical 10.0)
- [CVE-2005-4727](https://insights.sbomify.com/CVE-2005-4727/): Cross-site scripting in n/a (medium 5.1)
- [CVE-2004-2351](https://insights.sbomify.com/CVE-2004-2351/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2352 and fix it if it is affected.

What it is: CVE-2004-2352 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-2352 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-2004-2352/ (Markdown: https://insights.sbomify.com/CVE-2004-2352/index.md)
```

## Sources

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

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