# CVE-2003-0590: Cross-site scripting in n/a

> Remote attackers can inject arbitrary HTML and scripts via the post icon field in Splatt Forum, requiring user interaction to execute.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2016
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rxhc-8rp7-6c23

## What is CVE-2003-0590?

CVE-2003-0590 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Oct 2016. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in Splatt Forum allows remote attackers to insert arbitrary HTML and web script via the post icon (image_subject) field.

## Which versions are affected by CVE-2003-0590?

It affects 1 product.


Products: Splatt Splatt Forum.

## How do I fix CVE-2003-0590?

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

## Is CVE-2003-0590 being exploited?

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

Public exploit code:

- Splatt Forum 3/4 - Post Icon HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0959](https://insights.sbomify.com/CVE-2002-0959/): Cross-site scripting in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0590 and fix it if it is affected.

What it is: CVE-2003-0590 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Oct 2016. Any signed-in user can exploit it over the network, 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-2003-0590 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-2003-0590/ (Markdown: https://insights.sbomify.com/CVE-2003-0590/index.md)
```

## Sources

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

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