CVE-2023-3590
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 · uneditedMattermost fails to delete card attachments in Boards, allowing an attacker to access deleted attachments.
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 confidenceMattermost Boards contains a vulnerability where card attachments are not properly deleted when cards are deleted, leaving the attachment files accessible even after the card deletion. This indicates a logic flaw in the deletion workflow where the file references or actual files in storage are not being cleaned up or access-controlled properly.
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>= 7.10.0, < 7.10.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Mattermost Server versionLog into the Mattermost System Console and navigate to About > Mattermost, or use the command `mmctl version` or check the /opt/mattermost/version file to determine the installed server versionAffected if The installed version is 7.10.0, 7.10.1, or 7.10.2 (any version >= 7.10.0 but < 7.10.3)
-
Confirm Boards plugin is enabledNavigate to System Console > Plugins > Plugin Management and verify the Boards plugin (focalboard) is installed and enabled, or check the focalboard plugin directory exists in the plugins folderAffected if The Boards plugin is enabled and in use on the server
-
Identify Boards file storage locationCheck the Mattermost config.json for the 'FileSettings > Directory' path (typically /opt/mattermost/data or similar), then locate the focalboard subdirectory which contains board attachmentsAffected if File storage is configured and accessible for inspection
-
Inspect for orphaned attachment filesReview the focalboard attachments directory for files that may remain after their parent cards have been deleted from boards - compare file listings against current board/card database recordsAffected if Attachment files exist in storage that are no longer referenced by any current card in the Boards database
You are affected if running Mattermost Server version 7.10.0 through 7.10.2 with the Boards plugin enabled and you find orphaned files in the Boards attachment storage that are no longer linked to any existing card.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.10.3
Review and restrict access to the file storage backend where Board attachments are stored, and apply any available Mattermost security updates that address proper deletion of card attachments in Boards.
7.10.3
- Ensure you have a backup of your Mattermost Server data and configuration before proceeding
- Review the Mattermost upgrade documentation for your deployment method (manual, Docker, or package manager)
- Upgrade Mattermost Server to version 7.10.3 or later
- Verify the upgrade was successful by checking the server version in the system console
- Test that Boards functionality is working correctly, particularly card attachment operations
- Confirm that the authorization fix is properly applied by verifying deleted attachments can no longer be accessed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3590 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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