What is CVE-2016-1000227?

CVE-2016-1000227 is a high-severity cross-site scripting (XSS) vulnerability in bootstrap-tagsinput (npm), affecting versions <= 0.8.0. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of bootstrap-tagsinput are affected by CVE-2016-1000227?

bootstrap-tagsinput (npm) versions <= 0.8.0 is affected.

Is there a fix for CVE-2016-1000227?

No fixed version is listed for CVE-2016-1000227 yet. Monitor the advisory for updates and apply mitigations in the interim.

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

Whether CVE-2016-1000227 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-1000227 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-1000227?

No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.

CVE-2016-1000227 in bootstrap-tagsinput

Q: Which versions of bootstrap-tagsinput are affected by CVE-2016-1000227?

bootstrap-tagsinput (npm) versions <= 0.8.0 is affected.

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

No fixed version is listed for CVE-2016-1000227 yet. Monitor the advisory for updates and apply mitigations in the interim.

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

Whether CVE-2016-1000227 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-1000227 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-1000227?

No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.

Summary

Cross-Site Scripting in bootstrap-tagsinput

All versions of bootstrap-tagsinput are vulnerable to cross-site scripting when user input is passed into the itemTitle parameter unmodified, as the package fails to properly sanitize or encode user input for that parameter.

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.

Affected versions

bootstrap-tagsinput (<= 0.8.0)

Security releases

Not available

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

This package is not actively maintained, and has not seen an update since 2015.

Because of this, the simplest mitigation is to avoid using the itemTitle parameter. With over 200 open issues and over 100 open pull requests as of 2/2018, it seems unlikely that the author has any intention of maintaining the module. If avoiding the use of itemTitle indefinitely is acceptable, this is a workable solution. If not, the best available mitigation is to use a fork of the module that is actively maintained and provides similar functionality. There are many such forks to choose from available on github..

Frequently Asked Questions

What is CVE-2016-1000227? CVE-2016-1000227 is a high-severity cross-site scripting (XSS) vulnerability in bootstrap-tagsinput (npm), affecting versions <= 0.8.0. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of bootstrap-tagsinput are affected by CVE-2016-1000227? bootstrap-tagsinput (npm) versions <= 0.8.0 is affected.
Is there a fix for CVE-2016-1000227? No fixed version is listed for CVE-2016-1000227 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2016-1000227 exploitable, and should I be worried? Whether CVE-2016-1000227 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-1000227 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-1000227? No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.