Cyber Resilience

CVE-2025-55073

Access Control in Mattermost Server 10.5.0 – 10.5.12

Published
14 November 2025
Modified
19 November 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS Score 0.0018 8th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-55073 is a medium-severity Missing Authentication for Critical Function (CWE-306) vulnerability in Mattermost Mattermost Server. Its CVSS base score is 5.4 (Medium).

Operationally, ranked at the 8th 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 AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Mattermost versions 10.11.x <= 10.11.3, 10.5.x <= 10.5.11, 10.12.x <= 10.12.0 fail to validate the relationship between the post being updated and the MSTeams plugin OAuth flow which allows an attacker to edit arbitrary posts via a crafted MSTeams plugin…

more

OAuth redirect URL.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-6226Same product: Mattermost Mattermost Server
CVE-2025-25068Same product: Mattermost Mattermost Server
CVE-2025-13870Same product: Mattermost Mattermost Server
CVE-2026-6673Same product: Mattermost Mattermost Server
CVE-2025-55070Same product: Mattermost Mattermost Server
CVE-2025-27538Same product: Mattermost Mattermost Server
CVE-2025-47870Same product: Mattermost Mattermost Server
CVE-2024-2450Same product: Mattermost Mattermost Server
CVE-2026-6343Same product: Mattermost Mattermost Server
CVE-2026-2462Same product: Mattermost Mattermost Server

Affected Assets

mattermost
mattermost server
10.5.0 — 10.5.12 · 10.11.0 — 10.11.4 · 10.12.0 — 10.12.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • SI-10 Information Input Validation
  • SC-23 Session Authenticity
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.3
  • V6.4.4
  • V10.4.16
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization checks to ensure only the legitimate owner can update a post, blocking the unauthorized edit via the crafted MSTeams OAuth redirect.

prevent

Requires validation of all input data (including OAuth redirect parameters) to confirm the relationship between the post and the authenticated session before allowing the update.

prevent

Protects session authenticity during the OAuth flow so an attacker cannot inject a forged redirect that bypasses the intended post-to-user binding.

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.AA-03 full match
prevents

Directly requires authentication of users/services/hardware, which eliminates missing authentication for critical functions.

PR.AA-01 partial match
prevents

Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.

PR.AA-05 partial match
prevents

Defining and enforcing authorizations assumes prior authentication and therefore only partially mitigates the absence of authentication.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized access can be undermined by missing authentication but does not address the root authentication gap.

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.

prevents

The control explicitly calls for authentication before any critical function is reached, eliminating the possibility of bypassing authentication for high-value operations.

prevents

Mandating authentication requirements for critical functions at the requirements-gathering stage ensures that essential operations are not left unprotected by missing login or verification mechanisms.

mitigates

Mandating authentication for network services and critical functions stops attackers from invoking sensitive operations without credentials, closing gaps where authentication is absent for important capabilities.

prevents

Security engineering principles insist on authentication and authorization for every critical function, eliminating entry points that lack any access control mechanism.

none

Requiring strong authentication and access-privilege enablement for remote connections ensures that critical functions cannot be invoked without proper verification, closing a gap that would otherwise allow unauthenticated use.

none

Mandatory use of access cards, biometrics, or two-factor authentication ensures that critical physical areas cannot be entered without proper authentication.

References