What is CVE-2016-15010?

CVE-2016-15010 is a medium-severity cross-site scripting (XSS) vulnerability in django-ucamlookup (pip), affecting versions < 1.9.2. It is fixed in 1.9.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2016-15010?

CVE-2016-15010 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of django-ucamlookup are affected by CVE-2016-15010?

django-ucamlookup (pip) versions < 1.9.2 is affected.

Is there a fix for CVE-2016-15010?

Yes. CVE-2016-15010 is fixed in 1.9.2. Upgrade to this version or later.

Is CVE-2016-15010 exploitable, and should I be worried?

Whether CVE-2016-15010 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2016-15010 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2016-15010 in django-ucamlookup

Q: How severe is CVE-2016-15010?

CVE-2016-15010 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of django-ucamlookup are affected by CVE-2016-15010?

django-ucamlookup (pip) versions < 1.9.2 is affected.

Q: Is there a fix for CVE-2016-15010?

Yes. CVE-2016-15010 is fixed in 1.9.2. Upgrade to this version or later.

Q: Is CVE-2016-15010 exploitable, and should I be worried?

Whether CVE-2016-15010 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2016-15010 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2016-15010?

Upgrade django-ucamlookup to 1.9.2 or later.

Summary

django-ucamlookup Cross-site Scripting vulnerability

A vulnerability classified as problematic was found in University of Cambridge django-ucamlookup up to 1.9.1. Affected by this vulnerability is an unknown functionality of the component Lookup Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. Upgrading to version 1.9.2 can address this issue. The name of the patch is 5e25e4765637ea4b9e0bf5fcd5e9a922abee7eb3. It is recommended to upgrade the affected component. The identifier VDB-217441 was assigned to this vulnerability.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2016-15010 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.9.2); upgrading removes the vulnerable code path.

Affected versions

django-ucamlookup (< 1.9.2)

Security releases

django-ucamlookup → 1.9.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade django-ucamlookup to 1.9.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2016-15010? CVE-2016-15010 is a medium-severity cross-site scripting (XSS) vulnerability in django-ucamlookup (pip), affecting versions < 1.9.2. It is fixed in 1.9.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2016-15010? CVE-2016-15010 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of django-ucamlookup are affected by CVE-2016-15010? django-ucamlookup (pip) versions < 1.9.2 is affected.
Is there a fix for CVE-2016-15010? Yes. CVE-2016-15010 is fixed in 1.9.2. Upgrade to this version or later.
Is CVE-2016-15010 exploitable, and should I be worried? Whether CVE-2016-15010 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2016-15010 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2016-15010? Upgrade django-ucamlookup to 1.9.2 or later.