CVE-2022-46148
Summary
| CVE | CVE-2022-46148 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-11-29 17:15:00 UTC |
| Updated | 2022-12-01 22:02:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-79
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Discourse | Discourse | 2.9.0 | beta1 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta10 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta11 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta2 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta3 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta4 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta5 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta6 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta7 | All | All |
| Application | Discourse | Discourse | 2.9.0 | beta8 | All | All |
| Application | Discourse | Discourse | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Self-XSS through malicious composer message · Advisory · discourse/discourse · GitHub | CONFIRM | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.