CVE-2023-46998: Bootbox.js Cross Site Scripting vulnerability

bootbox Updated 02 Oct 2025

Summary

14/11/2023
No i
Moderate
6.1

CVE-2023-46998: Bootbox.js Cross Site Scripting vulnerability. Affects bootbox versions >= 3.2.0, <= 6.0.0. No fix is published. How to fix ↓

Also tracked for

The same CVE-2023-46998 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Bootbox.js is an open-source JavaScript library that provides a set of enhanced modal dialogs for web applications. It is commonly used to create alert, confirm, and prompt dialogs with customizable styles and functionality. The library is available as an npm package and is widely adopted by developers for its simplicity and ease of use. However, versions 3.2 through 6.0 of Bootbox.js are vulnerable to a Cross Site Scripting (XSS) attack, which can allow a remote attacker to execute arbitrary code by exploiting the alert(), confirm(), and prompt() functions.

Vulnerability Detail

The Cross Site Scripting vulnerability in Bootbox.js arises from improper input sanitization and validation. When a crafted payload is passed to the affected functions, the library fails to properly escape or sanitize the input, allowing malicious code to be executed within the context of the user's browser. This can lead to various security risks, including the theft of sensitive information, session hijacking, and unauthorized actions on behalf of the user. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, developers can manually sanitize and escape user input before passing it to the affected functions in Bootbox.js. This can be achieved by using appropriate HTML encoding or escaping functions provided by the programming language or framework being used. However, it is strongly recommended to apply the official fix by updating to a patched version of Bootbox.js as soon as possible.

Conclusion

In conclusion, the Cross Site Scripting vulnerability in Bootbox.js versions 3.2 through 6.0 poses a moderate security risk, allowing remote attackers to execute arbitrary code within the user's browser. To mitigate this risk, it is crucial to update to Bootbox.js version 6.1.0 or later, which includes a fix for the XSS vulnerability. Developers should also ensure proper input sanitization and validation in their applications to prevent similar security issues. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for bootbox →

Share this vulnerability

FAQ

Bootbox.js is a JavaScript library that provides enhanced modal dialogs for web applications, such as alert, confirm, and prompt dialogs.

Versions 3.2.0 through 6.0.0 of Bootbox.js are affected by this Cross Site Scripting vulnerability.

The vulnerability allows remote attackers to execute arbitrary code within the user's browser, potentially leading to information theft, session hijacking, and unauthorized actions.

Yes, a fix has been released in Bootbox.js version 6.1.0, which implements proper input sanitization and validation to mitigate the XSS vulnerability.

To update Bootbox.js, you can use the package manager for your project (e.g., npm) and specify the desired version (e.g., 'npm install bootbox@6.1.0').

Related vulnerabilities

Recent vulnerabilities recorded for bootbox.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback