CVE-2023-28318
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 · uneditedA vulnerability has been discovered in Rocket.Chat, where messages can be hidden regardless of the Message_KeepHistory or Message_ShowDeletedStatus server configuration. This allows users to bypass the intended message deletion behavior, hiding messages and deletion notices.
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 confidenceRocket.Chat contains a vulnerability where users can hide messages regardless of the Message_KeepHistory or Message_ShowDeletedStatus server configuration settings. This allows bypassing the intended message deletion behavior, enabling users to hide both messages and deletion notices.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Rocket.Chat installationIdentify the Rocket.Chat instance in your environment by checking running processes, services, or installation directories commonly used (such as /opt/Rocket.Chat, /var/www/rocket.chat, or Docker containers)Affected if Rocket.Chat is installed and running
-
Verify Message_KeepHistory configurationAccess Rocket.Chat admin settings and check the value of the Message_KeepHistory setting in the server configurationAffected if Message_KeepHistory is enabled (set to true) but users can still hide messages without proper deletion behavior being enforced
-
Verify Message_ShowDeletedStatus configurationAccess Rocket.Chat admin settings and check the value of the Message_ShowDeletedStatus setting in the server configurationAffected if Message_ShowDeletedStatus is enabled (set to true) but deletion notices are not being shown as expected when users hide messages
-
Inspect for hidden messages in databaseQuery the Rocket.Chat database (typically MongoDB) for messages where the hidden or tshow field indicates the message has been hidden from normal viewAffected if Hidden messages exist in the database that bypass the intended configuration settings
-
Review user message hiding activityCheck admin logs, audit trails, or user activity records for instances where users hid messages (as opposed to formally deleting them)Affected if Users have been able to hide messages without triggering the expected Message_KeepHistory or Message_ShowDeletedStatus behavior
If Rocket.Chat is installed and users have been able to hide messages while the Message_KeepHistory or Message_ShowDeletedStatus settings are not being properly enforced, the environment is affected by this CVE.
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.
From vendor dataApply the vendor-provided patch or updated version of Rocket.Chat that addresses this vulnerability. Monitor user activity for unauthorized message hiding while awaiting the patch.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28318 — 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-28318 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