How severe is CVE-2015-3219?

CVE-2015-3219 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2015-3219?

CVE-2015-3219 affects the following packages: horizon (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-3219?

Update horizon to 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-3219 is resolved across your whole dependency graph.

How do I detect CVE-2015-3219 in my PyPI dependencies?

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

How do I mitigate CVE-2015-3219 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-2015-3219 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-3219, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-3219?

CVE-2015-3219 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 88th 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-2015-3219?

CVE-2015-3219 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-2015-3219 published, and has it been updated?

CVE-2015-3219 was published on August 20, 2015 and was last updated on April 10, 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

MEDIUM severity

CVE-2015-3219 — horizon

MEDIUMFix: openstack/horizon@28d8f49

CVE-2015-3219 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in horizon. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for horizon — see the affected versions and patch details below.

OpenStack Dashboard (Horizon) Cross-site scripting (XSS) vulnerability

Also known asGHSA-rhjj-f6gq-6gx2PYSEC-2015-40

Published

Aug 20, 2015

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍horizon

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 the Orchestration/Stack section in OpenStack Dashboard (Horizon) 2014.2 before 2014.2.4 and 2015.1.x before 2015.1.1 allows remote attackers to inject arbitrary web script or HTML via the description parameter in a heat template, which is not properly handled in the help_text attribute in the Field class.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`horizon`	all versions	8.0.0a0`pip install --upgrade 'horizon==8.0.0a0'`

Affected Products

3 products · 7 configurations

debian linuxdebian

1 version

8.0

Application

horizonopenstack

5 versions

2014.2.02014.2.12014.2.22014.2.32015.1.0

solarisoracle

1 version

11.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site scripting (XSS) vulnerability in the Orchestration/Stack sect…

bugs.launchpad.netNVDDec 2016

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for horizon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update horizon to 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-3219 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`python-django-horizon-0:2014.2.3-7.el7ost`	RHSA-2015:1679

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-3219 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

horizon

3.5/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Aug 20, 2015

First exploit

Dec 24, 2016

Last updated

Apr 10, 2026

Identifiers

CVE-2015-3219

GHSA-rhjj-f6gq-6gx2

PYSEC-2015-40

References

Advisorylists.openstack.org Advisoryrhn.redhat.com · RHSA 2015 1679 Advisorydebian.org · dsa 3617 Advisoryoracle.com · bulletinjul2015 2511963 Advisorysecurityfocus.com Advisorybugs.launchpad.net Advisorynvd.nist.gov · CVE 2015 3219 Fixopenwall.com Webgithub.com · 28d8f49786d6df297b2574514916fa782e941e09 Webgithub.com · 84da479739fbfff75d9492d00fd0ed1a31ea52b3 Webgithub.com · dab92e7d2f576caea8f81c8e22a516fb45633794 Webgithub.com · PYSEC 2015 40.yaml Packagegithub.com · horizon

Related vulnerabilities

This CVE is medium severity, in line with the other 8 CVEs affecting horizon.

CVE-2026-55748CVE-2026-43002CVE-2022-45582CVE-2020-29565CVE-2012-2094CVE-2012-2144CVE-2017-7400CVE-2014-0157

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026