# CVE-2011-0728: Loggerhead XSS via filename

> Authenticated users can inject arbitrary scripts via filenames in Loggerhead revision views, potentially compromising other users' sessions.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/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:** Yes
- **Published:** 29 Mar 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-0728, GHSA-qjmg-77xh-7mjw, PYSEC-2026-840

## What is CVE-2011-0728?

CVE-2011-0728 is a low-severity cross-site scripting vulnerability in n/a, published on 29 Mar 2011. 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 templatefunctions.py in Loggerhead before 1.18.1 allows remote authenticated users to inject arbitrary web script or HTML via a filename, which is not properly handled in a revision view.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2011-0728?

3 open source packages ship an affected version, including loggerhead. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `loggerhead` | PyPI | All versions | 1.18.1 |
| `loggerhead` | PyPI | All versions | 1.18.1 |
| `loggerhead` | PyPI | All versions | 1.18.1 |

Products: Michael Hudson-Doyle Loggerhead.

## How do I fix CVE-2011-0728?

Upgrade loggerhead to 1.18.1 or later.

## Is CVE-2011-0728 being exploited?

There is no known exploitation of CVE-2011-0728 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0728 and fix it if it is affected.

What it is: CVE-2011-0728 is a low-severity cross-site scripting vulnerability in n/a, published on 29 Mar 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-0728 in the wild and no public exploit code.

Affected packages and fixed versions:
- loggerhead (PyPI): affected all versions; fixed in 1.18.1
- loggerhead (PyPI): affected all versions; fixed in 1.18.1
- loggerhead (PyPI): affected all versions; fixed in 1.18.1

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-2011-0728/ (Markdown: https://insights.sbomify.com/CVE-2011-0728/index.md)
```

## Sources

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

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