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

> Remote attackers can execute arbitrary web script or HTML in other users' browsers via a malicious URL in AN HTTP server.

- **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:** 16 Nov 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pgrc-mhqr-gxg2

## What is CVE-2003-1271?

CVE-2003-1271 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Nov 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

Cross-site scripting vulnerability (XSS) in AN HTTP 1.41e allows remote attackers to execute arbitrary web script or HTML as other users via a URL containing the script.

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

It affects 1 product.


Products: An An-Http.

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

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

## Is CVE-2003-1271 being exploited?

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

Public exploit code:

- AN HTTPD 1.41 e - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1269](https://insights.sbomify.com/CVE-2003-1269/): Information disclosure in n/a (medium 5.0)
- [CVE-2003-1270](https://insights.sbomify.com/CVE-2003-1270/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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