LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31060: Banner topic data is exposed on login-required Discourse sites

Discourse is an open-source discussion platform. Prior to version 2.8.4 in the `stable` branch and version `2.9.0.beta5` in the `beta` and `tests-passed` branches, banner topic data is exposed on login-required sites. This issue is patched in version 2.8.4 in the `stable` branch and version `2.9.0.beta5` in the `beta` and `tests-passed` branches of Discourse. As a workaround, one may disable banners.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A private Discourse forum could leak banner topic information to people who are not logged in. The issue affects older Discourse versions and is fixed in named stable and beta releases. Business impact depends on whether banner topics contain sensitive internal announcements, customer information, or operational details.

Executive priority

Handle as a moderate privacy and confidentiality issue. Patch during the normal security maintenance window, or accelerate if private forum banners may contain sensitive business, customer, or operational information.

Technical view

CVE-2022-31060 is a CWE-200 information exposure in Discourse. On login-required sites, banner topic data was exposed without authentication before stable 2.8.4 and beta/tests-passed 2.9.0.beta5. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, and confidentiality impact only.

Likely exposure

Exposure is likely limited to Discourse deployments requiring login, running affected versions, and using banner topics. Public forums or sites without banners may have lower practical impact, but the source bundle does not fully define all deployment conditions.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The CVSS vector indicates unauthenticated network access may be enough to observe exposed banner topic data, but no exploit procedure is provided in the cited sources.

Researcher notes

Focus review on login-required Discourse sites and banner topic behavior. The patch references point to the advisory, pull request, and commit, but the bundle does not include independent exploitation reports or broader product impact.

Mitigation direction

  • Upgrade stable Discourse deployments to version 2.8.4 or later.
  • Upgrade beta or tests-passed deployments to 2.9.0.beta5 or later.
  • Disable banners as the documented workaround if immediate upgrade is not possible.
  • Review vendor advisory and release notes before applying production changes.

Validation and detection

  • Inventory Discourse branch and version across login-required sites.
  • Check whether affected sites use banner topics.
  • Confirm upgraded sites run stable 2.8.4 or beta/tests-passed 2.9.0.beta5 or later.
  • Verify unauthenticated visitors cannot view banner topic data after remediation.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31060 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-31060Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
discoursediscoursestable < 2.8.4, beta <= 2.9.0.beta4, tests-passed <= 2.9.0.beta4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.