# CVE-2004-1703: Cross-site request forgery in n/a

> Attackers can force logged-in administrators to create unauthorized user accounts via malicious image tags in comments.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 26 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-grc6-2v8g-8xww

## What is CVE-2004-1703?

CVE-2004-1703 is a high-severity vulnerability in n/a, published on 26 Feb 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

Fusion News 3.6.1 allows remote attackers to add user accounts, if the administrator is logged in, via a comment that contains an img bbcode tag that calls index.php with the signup action, which is executed when the administrator's browser loads the page with the img tag.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Fusionphp Fusion News.

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

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

## Is CVE-2004-1703 being exploited?

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

Public exploit code:

- Fusionphp Fusion News 3.3/3.6 - Administrator Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4240](https://insights.sbomify.com/CVE-2006-4240/): Code injection in n/a (high 7.5)
- [CVE-2006-3387](https://insights.sbomify.com/CVE-2006-3387/): Path traversal in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1703 is a high-severity vulnerability in n/a, published on 26 Feb 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1703 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-1703/ (Markdown: https://insights.sbomify.com/CVE-2004-1703/index.md)
```

## Sources

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

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