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

> Remote attackers can inject arbitrary web script or HTML via specific parameters in the Bluemoon PopnupBLOG module for XOOPS.

- **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:** 11 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7qgq-w6fc-rgcq

## What is CVE-2008-4053?

CVE-2008-4053 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Sep 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 index.php in the Bluemoon PopnupBLOG module 3.20 and 3.30 for XOOPS allow remote attackers to inject arbitrary web script or HTML via the (1) param, (2) cat_id, and (3) view parameters.

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

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

It affects 1 product.


Products: Bluemoon Popnupblog.

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

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

## Is CVE-2008-4053 being exploited?

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

Public exploit code:

- Bluemoon inc. PopnupBlog 3.30 - 'index.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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