How severe is GHSA-pj7m-g53m-7638?

GHSA-pj7m-g53m-7638 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-pj7m-g53m-7638?

GHSA-pj7m-g53m-7638 affects the following packages: org.webjars:bootstrap (Maven), bootstrap (npm), bootstrap (NuGet), bootstrap.sass (NuGet), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), and 2 more. Ecosystems affected: Maven, npm, NuGet, Packagist, RubyGems.

How do I fix GHSA-pj7m-g53m-7638?

Update org.webjars:bootstrap to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pj7m-g53m-7638 is resolved across your whole dependency graph.

How do I detect GHSA-pj7m-g53m-7638 in my Maven, npm, NuGet, Packagist, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars:bootstrap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pj7m-g53m-7638 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-pj7m-g53m-7638 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-pj7m-g53m-7638, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-pj7m-g53m-7638?

GHSA-pj7m-g53m-7638 has an EPSS (Exploit Prediction Scoring System) score of 4.3%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pj7m-g53m-7638?

GHSA-pj7m-g53m-7638 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pj7m-g53m-7638 published, and has it been updated?

GHSA-pj7m-g53m-7638 was published on September 13, 2018 and was last updated on November 20, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven📦 npm.NET NuGet🐘 Packagist💎 RubyGems

Not in CISA KEV

MEDIUM severity

Bootstrap Cross-site Scripting vulnerabilityGHSA-pj7m-g53m-7638

MEDIUMFix: twbs/bootstrap#26630

GHSA-pj7m-g53m-7638 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.webjars:bootstrap. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.webjars:bootstrap — see the affected versions and patch details below.

Also known asCVE-2018-14041

Published

Sep 13, 2018

Updated

Nov 20, 2025

Affected

10 pkgs

Patched

10 / 10

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

10 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

15Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

bootstrapnpm

8.1Mdownloads / week

Description

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.

Affected Packages

10 total 10 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.webjars:bootstrap`	≥ 4.0.0&&< 4.1.2	4.1.2`org.webjars:bootstrap:4.1.2`
📦npm	`bootstrap`	≥ 4.0.0&&< 4.1.2	4.1.2`npm install bootstrap@4.1.2`
.NETNuGet	`bootstrap`	≥ 4.0.0&&< 4.1.2	4.1.2`dotnet add package bootstrap --version 4.1.2`
.NETNuGet	`bootstrap.sass`	≥ 4.0.0&&< 4.1.2	4.1.2`dotnet add package bootstrap.sass --version 4.1.2`
🐘Packagist	`typo3/cms-core`	≥ 8.0.0&&< 8.7.23	8.7.23`composer require typo3/cms-core:^8.7.23`
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 9.5.4	9.5.4`composer require typo3/cms-core:^9.5.4`

Affected Products

1 product · 10 configurations

Application

bootstrapgetbootstrap

≥ 4.0.0 && < 4.1.2

1 version

4.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Bootstrap before 4.1.2, XSS is possible in the data-target property o…

github.comNVDJun 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars:bootstrap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.webjars:bootstrap to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pj7m-g53m-7638 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 7.4.9	`org.jboss.hal/hal-console:3.3.16.Final-redhat-00001`	RHSA-2023:0556
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-hal-console-0:3.3.16-1.Final_redhat_00001.1.el8eap`	RHSA-2023:0553
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9	`eap7-hal-console-0:3.3.16-1.Final_redhat_00001.1.el9eap`	RHSA-2023:0554
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7	`eap7-hal-console-0:3.3.16-1.Final_redhat_00001.1.el7eap`	RHSA-2023:0552
Red Hat Single Sign-On 7.3.2 zip	`bootstrap`	RHSA-2019:1456

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-pj7m-g53m-7638 in your dependencies?

Find it across Maven, npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works