dbcve.org
MattermostApplication

CVE-2023-4108

HIGH · 7.5 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 7.8.8 / 7.9.6 or later.
See remediation →
84/100
Remediation priority · High
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 fails to sanitize post metadata during audit logging resulting in permalinks contents being logged

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 · moderate confidence

Mattermost's audit logging system does not properly sanitize post metadata before写入审计日志，导致永久链接（permalink）内容被记录下来。这可能允许未经授权的用户通过访问审计日志查看原本不应暴露的敏感信息，如私有频道的永久链接URL。

Mitigation升级到Mattermost已发布的安全更新版本；在此之前，严格限制对审计日志的访问权限，并监控日志访问行为。

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
MattermostApplication
Affected:>= 7.8.0, < 7.8.8>= 7.9.0, < 7.9.6>= 7.10.0, < 7.10.4

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Mattermost version
    Run 'mattermost version' or check the version displayed in the system console under About > Mattermost. Alternatively, check the version from the package manager or docker image tag.
    Affected if The installed version falls within 7.8.0-7.8.7, 7.9.0-7.9.5, or 7.10.0-7.10.3 (versions prior to the fixed releases 7.8.8, 7.9.6, and 7.10.4).
  2. Confirm audit logging is enabled
    Navigate to System Console > Audits and Logging > Logging, or check the config.json file for 'LogSettings.EnableAudit' set to true.
    Affected if Audit logging is enabled (the vulnerability only applies when audit logging is active).
  3. Verify audit log storage configuration
    Check the audit log file location in config.json under 'LogSettings.AuditFileSettings' or view in System Console. Ensure you can access the audit log files.
    Affected if Audit logs are being written to storage (the flaw allows sensitive permalink content to be recorded in these logs).
  4. Inspect audit logs for permalink content
    Search audit log files for patterns like '/pl/' (permalink path) or examine recent audit entries for 'post' event types to identify if post metadata with permalinks is being recorded.
    Affected if Audit logs contain unredacted permalink URLs from private channels, indicating the vulnerability is present and exploitable.

A user is affected if their Mattermost version is one of the vulnerable releases (7.8.x before 7.8.8, 7.9.x before 7.9.6, or 7.10.x before 7.10.4) AND audit logging is enabled, allowing potential exposure of private channel permalinks in accessible audit logs.

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 7.8.8 / 7.9.6 / 7.10.4 or later
Fixed in 7.8.87.9.67.10.4
Interim mitigation

升级到Mattermost已发布的安全更新版本；在此之前，严格限制对审计日志的访问权限，并监控日志访问行为。

Recommended fix High confidence

Mattermost 7.10.4 (or 7.8.8/7.9.6 depending on your current branch)

  1. 1. Backup your Mattermost instance database and configuration files
  2. 2. Download the appropriate Mattermost fixed version (7.8.8, 7.9.6, or 7.10.4) from the official Mattermost download page
  3. 3. Stop the Mattermost server
  4. 4. Upgrade Mattermost by following the official upgrade documentation for your deployment method
  5. 5. Verify the upgrade was successful by checking the server logs and testing core functionality
  6. 6. Confirm that audit logging no longer captures permalink contents in plaintext
Caveat Review Mattermost release notes for any breaking changes between your current version and the target upgrade version

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

Fix this in Mattermost Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4108 — 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-2023-4108 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