# CVE-2021-43353: Crisp Live Chat <= 0.31 Cross-Site Request Forgery to Stored Cross-Site Scripting

> Attackers can exploit missing nonce validation to inject arbitrary scripts via CSRF, potentially leading to stored XSS in the Crisp Live Chat plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 18 Jan 2022
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-mrwr-9wqr-6fc2

## What is CVE-2021-43353?

CVE-2021-43353 is a high-severity vulnerability in Crisp Live Chat, published on 18 Jan 2022. 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

The Crisp Live Chat WordPress plugin is vulnerable to Cross-Site Request Forgery due to missing nonce validation via the crisp_plugin_settings_page function found in the ~/crisp.php file, which made it possible for attackers to inject arbitrary web scripts in versions up to, and including 0.31.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-43353?

It affects 1 product.


Products: Crisp Crisp.

## How do I fix CVE-2021-43353?

No fix has been published for CVE-2021-43353 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-43353 being exploited?

There is no known exploitation of CVE-2021-43353 in the wild and no public exploit code.

## Other vulnerabilities in Crisp Live Chat

- [CVE-2024-27963](https://insights.sbomify.com/CVE-2024-27963/): WordPress Crisp – Live Chat and Chatbot plugin <= 0.44 - Cross Site Scripting (XSS) vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43353 and fix it if it is affected.

What it is: CVE-2021-43353 is a high-severity vulnerability in Crisp Live Chat, published on 18 Jan 2022. 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 CVE-2021-43353 in the wild and no public exploit code.

Affected product: Crisp Live Chat. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2021-43353/ (Markdown: https://insights.sbomify.com/CVE-2021-43353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-43353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-43353
- OSV: https://osv.dev/vulnerability/CVE-2021-43353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-43353/
Summaries are generated and may contain mistakes; the official description above is the record.