Cyber Resilience

CVE-2025-13352

Mattermost Server 10.11.0 – 10.11.7

Published
17 December 2025
Modified
29 December 2025
Patch / advisory
CVSS Score v3.1 3.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 25 floored blend · peak EPSS

Summary

CVE-2025-13352 is a low-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Mattermost Mattermost Server. Its CVSS base score is 3.0 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Mattermost versions 10.11.x <= 10.11.6 and Mattermost GitHub plugin versions <=2.4.0 fail to validate plugin bot identity in reaction forwarding which allows attackers to hijack the GitHub reaction feature to make users add reactions to arbitrary GitHub objects via crafted…

more

notification posts.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-2454Same product: Mattermost Mattermost Server
CVE-2025-12689Same product: Mattermost Mattermost Server
CVE-2026-25783Same product: Mattermost Mattermost Server
CVE-2025-20033Same product: Mattermost Mattermost Server
CVE-2025-20088Same product: Mattermost Mattermost Server
CVE-2024-54083Same product: Mattermost Mattermost Server
CVE-2025-41395Same product: Mattermost Mattermost Server
CVE-2025-20086Same product: Mattermost Mattermost Server
CVE-2025-20621Same product: Mattermost Mattermost Server
CVE-2026-4646Same product: Mattermost Mattermost Server

Affected Assets

mattermost
mattermost server
10.11.0 — 10.11.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input type validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect type-validation flaws but does not prevent them during development.

prevents

Secure development lifecycle mandates input validation and type checking to prevent improper type handling.

prevents

Application security requirements explicitly include validation of input data types and formats.

prevents

Secure architecture principles promote defensive input handling and type enforcement at system boundaries.

prevents

Secure coding standards directly require proper type validation of all external inputs.

References