# CVE-2023-2848: Cross-site request forgery in Movim

> Attackers can hijack WebSocket sessions in Movim due to missing header validation, potentially taking over user accounts.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **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:** 14 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-m9rr-h88h-h8w6, UBUNTU-CVE-2023-2848

## What is CVE-2023-2848?

CVE-2023-2848 is a high-severity vulnerability in Movim, published on 14 Sep 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

Movim prior to version 0.22 is affected by a Cross-Site WebSocket Hijacking vulnerability. This was the result of a missing header validation.

Weakness: CWE-346 (Origin Validation Error), CWE-1385 (Missing Origin Validation in WebSockets)

## Which versions are affected by CVE-2023-2848?

It affects 1 product.


Products: Movim Movim.

## How do I fix CVE-2023-2848?

Upgrade to a fixed version.

## Is CVE-2023-2848 being exploited?

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

## Other vulnerabilities in Movim

- [CVE-2017-5605](https://insights.sbomify.com/CVE-2017-5605/): XMPP Clients User Impersonation Vulnerability in Movim Moxl (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2848 and fix it if it is affected.

What it is: CVE-2023-2848 is a high-severity vulnerability in Movim, published on 14 Sep 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 CVE-2023-2848 in the wild and no public exploit code.

Affected product: Movim. 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-2023-2848/ (Markdown: https://insights.sbomify.com/CVE-2023-2848/index.md)
```

## Sources

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

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