# CVE-2022-24866: Exposure of Sensitive Information to an Unauthorized Actor in Discourse Assign

> An attacker can view private user and group information if the Discourse Assign plugin is configured for public access.

- **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:** 26 Apr 2022
- **Updated:** 23 Apr 2025

## What is CVE-2022-24866?

CVE-2022-24866 is a medium-severity vulnerability in discourse-assign, published on 26 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Discourse Assign is a plugin for assigning users to a topic in Discourse, an open-source messaging platform. Prior to version 1.0.1, the UserBookmarkSerializer serialized the whole User / Group object, which leaked some private information. The data was only being serialized to people who could view assignment info, which is limited to staff by default. For the vast majority of sites, this data was only leaked to trusted staff member, but for sites with assign features enabled publicly, the data was accessible to more people than just staff. Version 1.0.1 contains a patch. There are currently no known workarounds.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Discourse Assign.

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

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

## Is CVE-2022-24866 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24866 is a medium-severity vulnerability in discourse-assign, published on 26 Apr 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-24866 in the wild and no public exploit code.

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

## Sources

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

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