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

> Remote attackers can execute arbitrary scripts in the VirtuaNews Admin Panel via multiple parameters, potentially compromising admin accounts.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cwr5-qr66-jg4j

## What is CVE-2004-0358?

CVE-2004-0358 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Mar 2004. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in VirtuaNews Admin Panel Pro 1.0.3 allows remote attackers to execute arbitrary script as other users via (1) the mainnews parameter in admin.php, (2) the expand parameter in admin.php, (3) the id parameter in admin.php, (4) the catid parameter in admin.php, or (5) an unnamed parameter during the newslogo_upload action in admin.php.

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

It affects 1 product.


Products: Virtuasystems Virtuanews Pro.

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

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

## Is CVE-2004-0358 being exploited?

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

Public exploit code:

- VirtuaSystems VirtuaNews 1.0.x (Multiple Modules) - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0358 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Mar 2004. An attacker needs administrator access to exploit it, 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-2004-0358 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-2004-0358/ (Markdown: https://insights.sbomify.com/CVE-2004-0358/index.md)
```

## Sources

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

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