dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2024-11599

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-28
Fix available
A fix is available. Upgrade to 9.5.12 / 9.11.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Mattermost versions 10.0.x <= 10.0.1, 10.1.x <= 10.1.1, 9.11.x <= 9.11.3, 9.5.x <= 9.5.11 fail to properly validate email addresses which allows an unauthenticated user to bypass email domain restrictions via carefully crafted input on email registration.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Mattermost fails to properly validate email addresses during user registration, allowing unauthenticated attackers to bypass configured email domain restrictions using carefully crafted email input. This is a logical security control bypass rather than code execution, enabling unauthorized user registration into restricted installations.

MitigationUpgrade to Mattermost versions 10.0.2, 10.1.2, 9.11.4, or 9.5.12 or later which contain proper email validation. If upgrading is not immediately possible, consider disabling self-registration or adding supplemental authentication controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mattermost ServerApplication
Affected:>= 9.5.0, < 9.5.12>= 9.11.0, < 9.11.4>= 10.0.0, < 10.0.2>= 10.1.0, < 10.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mattermost Server version
    Access the Mattermost System Console and navigate to About > Edition and License, or use the CLI command: `mattermost version` or check the /api/v4/system/analytics endpoint
    Affected if The installed version falls within: 9.5.0-9.5.11, 9.11.0-9.11.3, 10.0.0-10.0.1, or 10.1.0-10.1.1
  2. Verify email domain restrictions are configured
    Navigate to System Console > User Authentication > Email, or check the SiteURL and Team settings. Alternatively, query the config via: `mattermost config get TeamSettings` or inspect the config.json file for RestrictCreationToDomains setting
    Affected if Email domain restrictions are configured (RestrictCreationToDomains is set to a non-empty value)
  3. Confirm user self-registration is enabled
    Navigate to System Console > User Authentication > Signup, or query: `mattermost config get ServiceSettings.EnableUserAccess` and `mattermost config get ServiceSettings.EnableEmailInvitations`
    Affected if Self-registration or email invitations are enabled, allowing new users to register without admin intervention

You are affected if your Mattermost Server version is within the vulnerable ranges AND email domain restrictions are configured AND self-registration is enabled, allowing an attacker to register with a restricted domain by bypassing email validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.5.12 / 9.11.4 / 10.0.2 or later
Fixed in 9.5.129.11.410.0.2
Interim mitigation

Upgrade to Mattermost versions 10.0.2, 10.1.2, 9.11.4, or 9.5.12 or later which contain proper email validation. If upgrading is not immediately possible, consider disabling self-registration or adding supplemental authentication controls.

Recommended fix High confidence

Upgrade to Mattermost Server 9.5.12, 9.11.4, 10.0.2, or 10.1.2 (whichever matches your current major.minor branch)

  1. Back up your Mattermost Server database and configuration files before upgrading
  2. Identify your current Mattermost version from the affected list (9.5.x, 9.11.x, 10.0.x, or 10.1.x)
  3. Download the appropriate fixed version: 9.5.12, 9.11.4, 10.0.2, or 10.1.2 (choose the version that corresponds to your current major.minor release)
  4. Follow the official Mattermost upgrade documentation for your installation method (e.g., Ansible, Docker, manual upgrade)
  5. After upgrade, verify that email domain restrictions are enforced correctly by attempting registration with domains that should be blocked
  6. Confirm the server starts successfully and test core functionality
Caveat Review Mattermost release notes for your target version for any breaking changes or required database migrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11599 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data