# GHSA-mrr8-v49w-3333: sweetalert2 contains potentially undesirable behavior

> The library executes undocumented audio/video actions on specific domains, requiring an upgrade to remove this undesirable behavior.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jul 2023

## What is GHSA-mrr8-v49w-3333?

GHSA-mrr8-v49w-3333 is a vulnerability in sweetalert2, published on 10 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

`sweetalert2` versions from 11.6.14 to before 11.22.4 have potentially undesirable behavior. The package outputs audio and/or video messages that do not pertain to the functionality of the package when run on specific tlds. This functionality is documented on the project's readme.

## Which versions are affected by GHSA-mrr8-v49w-3333?

2 open source packages ship an affected version, including sweetalert2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sweetalert2` | npm | From 11.6.14 | 11.22.4 |
| `sweetalert2` | npm | From 11.6.14 | 11.22.4 |

## How do I fix GHSA-mrr8-v49w-3333?

Upgrade sweetalert2 to 11.22.4 or later.

## Is GHSA-mrr8-v49w-3333 being exploited?

There is no known exploitation of GHSA-mrr8-v49w-3333 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mrr8-v49w-3333 and fix it if it is affected.

What it is: GHSA-mrr8-v49w-3333 is a vulnerability in sweetalert2, published on 10 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-mrr8-v49w-3333 in the wild and no public exploit code.

Affected packages and fixed versions:
- sweetalert2 (npm): affected from 11.6.14; fixed in 11.22.4
- sweetalert2 (npm): affected from 11.6.14; fixed in 11.22.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-mrr8-v49w-3333/ (Markdown: https://insights.sbomify.com/GHSA-mrr8-v49w-3333/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mrr8-v49w-3333

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mrr8-v49w-3333/
Summaries are generated and may contain mistakes; the official description above is the record.