Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 10 July 2023.
- Which products and versions are affected?
- sweetalert2 (npm) SEMVER:introduced=11.6.14,fixed=11.22.4.
- Is there a fix for This vulnerability?
- Yes. sweetalert2 (npm): upgrade to 11.22.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run sweetalert2 (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sweetalert2 (npm): upgrade to 11.22.4 or later
npm install sweetalert2@11.22.4
Technical details
The vulnerability (CWE-440: Unexpected Behavior) involves undesirable and undocumented code execution triggered by domain suffix matching. Specifically, the library would play audio/video messages unrelated to its alert dialog functionality when accessed from certain TLDs (.ru, .su, .рф). This behavior was triggered automatically on specific domains without user consent or clear application purpose, effectively injecting disruptive content into applications using the library. The issue affected versions 11.6.14 through 11.22.3 and was patched in 11.22.4 by removing the problematic code entirely.
Affected products
- sweetalert2 sweetalert2 11.6.14 to before 11.22.4
Timeline
- 2023-07-10: disclosed
- 2025-08-14: patched