What is CVE-2017-20182?

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

How severe is CVE-2017-20182?

CVE-2017-20182 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-ajax-utilities are affected by CVE-2017-20182?

django-ajax-utilities (pip) versions < 1.2.8 is affected.

Is there a fix for CVE-2017-20182?

Yes. CVE-2017-20182 is fixed in 1.2.8. Upgrade to this version or later.

Is CVE-2017-20182 exploitable, and should I be worried?

Whether CVE-2017-20182 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-2017-20182 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-2017-20182 in django-ajax-utilities

Q: How severe is CVE-2017-20182?

CVE-2017-20182 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-ajax-utilities are affected by CVE-2017-20182?

django-ajax-utilities (pip) versions < 1.2.8 is affected.

Q: Is there a fix for CVE-2017-20182?

Yes. CVE-2017-20182 is fixed in 1.2.8. Upgrade to this version or later.

Q: Is CVE-2017-20182 exploitable, and should I be worried?

Whether CVE-2017-20182 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-2017-20182 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-2017-20182?

Upgrade django-ajax-utilities to 1.2.8 or later.

Summary

Cross-site Scripting in django-ajax-utilities

A vulnerability was found in Mobile Vikings Django AJAX Utilities and classified as problematic. This issue affects the function Pagination of the file django_ajax/static/ajax-utilities/js/pagination.js of the component Backslash Handler. The manipulation of the argument url leads to cross site scripting. The attack may be initiated remotely. The patch is on commit 329eb1dd1580ca1f9d4f95bc69939833226515c9 which has been inclused in release 1.2.8. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-222611.

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-2017-20182 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.2.8); upgrading removes the vulnerable code path.

Affected versions

django-ajax-utilities (< 1.2.8)

Security releases

django-ajax-utilities → 1.2.8 (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-ajax-utilities to 1.2.8 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-2017-20182? CVE-2017-20182 is a medium-severity cross-site scripting (XSS) vulnerability in django-ajax-utilities (pip), affecting versions < 1.2.8. It is fixed in 1.2.8. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2017-20182? CVE-2017-20182 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-ajax-utilities are affected by CVE-2017-20182? django-ajax-utilities (pip) versions < 1.2.8 is affected.
Is there a fix for CVE-2017-20182? Yes. CVE-2017-20182 is fixed in 1.2.8. Upgrade to this version or later.
Is CVE-2017-20182 exploitable, and should I be worried? Whether CVE-2017-20182 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-2017-20182 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-2017-20182? Upgrade django-ajax-utilities to 1.2.8 or later.