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

> Remote attackers can trigger XSS, leak pathnames, and crash the MailPost server via crafted HTTP requests containing backslashes.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q6f4-4wv3-g4pv

## What is CVE-2004-1101?

CVE-2004-1101 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mailpost.exe in MailPost 5.1.1sv, and possibly earlier versions, allows remote attackers to cause a denial of service (server crash), leak sensitive pathname information in the resulting error message, and execute a cross-site scripting (XSS) attack via an HTTP request that contains a / (backslash) and arbitrary webscript before the requested file, which leaks the pathname and does not quote the script in the resulting Visual Basic error message.

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

It affects 1 product.


Products: Tips Mailpost.

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

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

## Is CVE-2004-1101 being exploited?

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

Public exploit code:

- TIPS MailPost 5.1.1 - Error Message Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1100](https://insights.sbomify.com/CVE-2004-1100/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2004-1102](https://insights.sbomify.com/CVE-2004-1102/): Information disclosure in n/a (medium 5.0)
- [CVE-2004-1103](https://insights.sbomify.com/CVE-2004-1103/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1101 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1101 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-1101/ (Markdown: https://insights.sbomify.com/CVE-2004-1101/index.md)
```

## Sources

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

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