CVE-2023-35075: Mattermost · Injection
Affects MattermostSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mattermost Mattermost | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Apply any official patches or updates from Mattermost as soon as they become available to ensure the issue is resolved at the source. 2) Implement strict access controls on who can create or rename channels within Mattermost to limit the ability of attackers to inject malicious HTML. 3) Monitor channel names for suspicious or unusual HTML content and enforce validation or sanitization policies at the application or proxy level if possible. 4) Educate users about the potential for UI manipulation and encourage vigilance against unexpected interface changes or phishing attempts within Mattermost. 5) Consider deploying Content Security Policy (CSP) headers to restrict the execution of inline scripts or loading of untrusted content, even though this vulnerability does not enable script execution directly. 6) Regularly audit Mattermost configurations and logs to detect any attempts to exploit this injection flaw. These steps go beyond generic advice by focusing on access control, monitoring, and user awareness tailored to the specific injection vector in Mattermost channel names.
Description
Mattermost fails to use innerText / textContent when setting the channel name in the webapp during autocomplete, allowing an attacker to inject HTML to a victim's page by create a channel name that is valid HTML. No XSS is possible though.