MediumGHSA-pj7m-g53m-7638CVE-2018-14041

Bootstrap Cross-site Scripting vulnerability

Published 13 Sept 2018 · Updated 20 Nov 2025

Affected packages

Affected
>=4.0.0 <4.1.2
Fixed in
4.1.2
Update to the fixed version for your release line, for example:npm install bootstrap@4.1.2
Affected
>=8.0.0 <8.7.23
Fixed in
8.7.23
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.23
Affected
>=9.0.0 <9.5.4
Fixed in
9.5.4
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.4
typo3/cmsComposer
Affected
>=8.0.0 <8.7.23
Fixed in
8.7.23
Update to the fixed version for your release line, for example:composer require typo3/cms:^8.7.23
typo3/cmsComposer
Affected
>=9.0.0 <9.5.4
Fixed in
9.5.4
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.4
Affected
>=4.0.0 <4.1.2
Fixed in
4.1.2
Update to the fixed version for your release line, for example:composer require twbs/bootstrap:^4.1.2

Details

In Bootstrap 4.x before 4.1.2, XSS is possible in the data-target property of scrollspy. This is similar to CVE-2018-14042.

Is GHSA-pj7m-g53m-7638 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.

References

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