# CVE-2008-3180: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via the pageid parameter or PATH_INFO in ContentNow CMS.

- **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:** 15 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gmpc-xgf5-4prf

## What is CVE-2008-3180?

CVE-2008-3180 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Jul 2008. 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 upload/file/language_menu.php in ContentNow CMS 1.4.1 allow remote attackers to inject arbitrary web script or HTML via the (1) pageid parameter or (2) PATH_INFO.

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

## Which versions are affected by CVE-2008-3180?

It affects 1 product.


Products: Cwh Underground Contentnow Cms.

## How do I fix CVE-2008-3180?

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

## Is CVE-2008-3180 being exploited?

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

Public exploit code:

- ContentNow 1.4.1 - Arbitrary File Upload / Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3180 and fix it if it is affected.

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

## Sources

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

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