How severe is CVE-2011-0728?

No CVSS score has been assigned to CVE-2011-0728 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-0728?

CVE-2011-0728 affects the following packages: loggerhead (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2011-0728?

Update loggerhead to 1.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-0728 is resolved across your whole dependency graph.

How do I detect CVE-2011-0728 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loggerhead, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-0728 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2011-0728 actively exploited in the wild?

No public exploit code has been indexed for CVE-2011-0728 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2011-0728?

CVE-2011-0728 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-0728?

CVE-2011-0728 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2011-0728 published, and has it been updated?

CVE-2011-0728 was published on March 29, 2011 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2011-0728 — loggerhead

CVE-2011-0728 is a Cross-site Scripting (XSS) vulnerability in loggerhead. A fix is available for loggerhead — see the affected versions and patch details below.

Loggerhead XSS via filename

Also known asGHSA-qjmg-77xh-7mjwPYSEC-2026-840

Published

Mar 29, 2011

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍loggerhead

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`loggerhead`	all versions	1.18.1`pip install --upgrade 'loggerhead==1.18.1'`

Affected Products

1 product · 5 configurations

Application

loggerheadmichael_hudson-doyle

≤ 1.18

4 versions

1.61.6.11.101.17

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loggerhead, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loggerhead to 1.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-0728 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-0728 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works