NVD / CVE Program· CNA GitHub_M

CVE-2022-46168: Group SMTP user emails are exposed in CC email header

Noroxi assessment

Priority: Monitor (action score 14/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
No fixed version is recorded, but the references include a patch (commit or PR) link.

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Discourse is an option source discussion platform. Prior to version 2.8.14 on the `stable` branch and version 2.9.0.beta15 on the `beta` and `tests-passed` branches, recipients of a group SMTP email could see the email addresses of all other users inside the group SMTP topic. Most of the time this is not an issue as they are likely already familiar with one another's email addresses. This issue is patched in versions 2.8.14 and 2.9.0.beta15. The fix is that someone sending emails out via group SMTP to non-staged users masks those emails with blind carbon copy (BCC). Staged users are ones that have likely only interacted with the group via email, and will likely include other people who were CC'd on the original email to the group. As a workaround, disable group SMTP for any groups that have it enabled.

LowCVSS 3.5 · v3.1—No exploit No fix recorded

Info leak

Published: Jan 5, 2023
Updated: Jun 17, 2026
EPSS: 0.5% · 45th percentile
CWE: CWE-359

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 14 / 40 · 3.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 3.5
CNA · GitHub_M: 3.5; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
discourse	discourse	cpe:2.3:a:discourse:discourse

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

discourse discoursebefore 2.8.14
discourse discourse2.9.0
discourse discourse3.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

discourse discourse
- < 2.8.14, >= 2.9.0.beta0, < 2.9.0.beta15affected

Same product

discourse: all records

Other highest-scoring records for the same primary product.

CVE-2021-41163RCE via malicious SNS subscription payload
45Plan
CVE-2025-68662FinalDestination hostname matching allows SSRF protection bypass
39Monitor
CVE-2023-47121Discourse SSRF vulnerability in Embedding
39Monitor

Published before and after this one in the same product

← EarlierCVE-2022-46150Nov 29, 2022 · Discourse may allow exposure of hidden tags in the subject of notification emails
17Monitor
← EarlierCVE-2022-46159Dec 2, 2022 · Any authenticated Discourse user can create an unlisted topic
17Monitor
Later →CVE-2022-23546Jan 5, 2023 · Discourse vulnerable to private topic leak via email#send_digest
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

discourse/discoursePR 19724

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope