MediumGHSA-4p24-vmcr-4gqjCVE-2016-10735

Bootstrap Cross-site Scripting vulnerability

Published 17 Jan 2019 · Updated 10 Sept 2026

Affected packages

bootstrapnpm

Affected: >=2.0.4 <3.4.0
Fixed in: 3.4.0

Update to the fixed version for your release line, for example:npm install bootstrap@3.4.0

bootstrapnpm

Affected: >=4.0.0-beta <4.0.0-beta.2
Fixed in: 4.0.0-beta.2

Update to the fixed version for your release line, for example:npm install bootstrap@4.0.0-beta.2

twbs/bootstrapComposer

Affected: >=2.0.4 <3.4.0
Fixed in: 3.4.0

Update to the fixed version for your release line, for example:composer require twbs/bootstrap:^3.4.0

twbs/bootstrapComposer

Affected: >=4.0.0-beta <4.0.0-beta.2
Fixed in: 4.0.0-beta.2

Update to the fixed version for your release line, for example:composer require twbs/bootstrap:^4.0.0-beta.2

bootstrap-sassnpm

Affected: >=2.0.4 <3.4.0
Fixed in: 3.4.0

Update to the fixed version for your release line, for example:npm install bootstrap-sass@3.4.0

Details

In Bootstrap 2.x from 2.0.4, 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute. Note that this is a different vulnerability than CVE-2018-14041.

See https://blog.getbootstrap.com/2018/12/13/bootstrap-3-4-0/ for more info.

Is GHSA-4p24-vmcr-4gqj in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected bootstrap, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.