# CVE-2022-41708: Missing authorization in relatedcode/Messenger

> Authenticated attackers can access other users' chats due to improper permission validation in the Messenger application.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-qrw5-w925-f5g8

## What is CVE-2022-41708?

CVE-2022-41708 is a medium-severity missing authorization vulnerability in relatedcode/Messenger, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Relatedcode's Messenger version 7bcd20b allows an authenticated external attacker to access existing chats in the workspaces of any user of the application. This is possible because the application does not validate permissions correctly.

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2022-41708?

It affects 1 product.


Products: Relatedcode Messenger.

## How do I fix CVE-2022-41708?

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

## Is CVE-2022-41708 being exploited?

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

## Other vulnerabilities in relatedcode/Messenger

- [CVE-2022-41707](https://insights.sbomify.com/CVE-2022-41707/): Information disclosure in relatedcode/Messenger (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41708 and fix it if it is affected.

What it is: CVE-2022-41708 is a medium-severity missing authorization vulnerability in relatedcode/Messenger, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41708 in the wild and no public exploit code.

Affected product: relatedcode/Messenger. 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-2022-41708/ (Markdown: https://insights.sbomify.com/CVE-2022-41708/index.md)
```

## Sources

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

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