CVE-2022-46148 Discourse allows self-XSS through malicious composer message

High 7.1 Published Updated

Attackers can trigger self-XSS via malicious drafts, leading to full XSS if Content Security Policy is modified or disabled.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2022-46148?

CVE-2022-46148 is a high-severity cross-site scripting vulnerability in Discourse Discourse, published on 29 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Discourse is an open-source messaging platform. In versions 2.8.10 and prior on the `stable` branch and versions 2.9.0.beta11 and prior on the `beta` and `tests-passed` branches, users composing malicious messages and navigating to drafts page could self-XSS. This vulnerability can lead to a full XSS on sites which have modified or disabled Discourse’s default Content Security Policy. This issue is patched in the latest stable, beta and tests-passed versions of Discourse.

Weakness: CWE-79

Which versions are affected by CVE-2022-46148?

1 open source package ship an affected version, including discourse. It affects 1 product.

PackageAffectedFixed in
discourse BitnamiAll versions2.8.11

Products include Discourse Discourse.

How do I fix CVE-2022-46148?

Upgrade discourse to 2.8.11 or later.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2022-46148 being exploited?

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

All Discourse Discourse vulnerabilities

Sources

Also known as BIT-discourse-2022-46148, GHSA-c5h6-6gg5-84fh.

Is CVE-2022-46148 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free