CVE-2023-28358
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 a markdown parsing issue in the "Search Messages" feature allows the insertion of malicious tags. This can be exploited on servers with content security policy disabled possible leading to some issues attacks like account takeover.
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 confidenceA markdown parsing flaw in Rocket.Chat's Search Messages feature allows injection of malicious HTML/script tags. When Content Security Policy (CSP) is disabled on the server, these injected tags can execute in users' browsers, potentially enabling session hijacking and account takeover via stolen cookies or tokens.
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< 6.0.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Determine installed Rocket.Chat versionAccess the Rocket.Chat administration panel (usually at /admin/info) or check the installed package version using your deployment method (docker inspect, package manager, or git commit). Compare the version number against the affected range: versions below 6.0.0 are potentially affected.Affected if Installed version is below 6.0.0
-
Verify the Search Messages feature is accessibleConfirm that the Rocket.Chat instance has the Search Messages feature enabled and accessible to users. This is typically found in the workspace under the search functionality.Affected if The Search Messages feature is enabled and users can perform message searches
-
Check Content Security Policy header configurationSend a request to the Rocket.Chat server (e.g., using curl -I https://your-rocket-chat-url) and inspect the HTTP response headers for the presence of Content-Security-Policy headers. Alternatively, check the server configuration files for CSP settings.Affected if CSP headers are absent from HTTP responses OR CSP is explicitly disabled in the server configuration
A user is affected if their Rocket.Chat installation is version below 6.0.0 AND the Search Messages feature is in use AND Content Security Policy headers are not configured/enabled on the server.
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 · scoped6.0.0
Enable and properly configure Content Security Policy (CSP) headers on the Rocket.Chat server to prevent execution of injected malicious scripts; also apply any available Rocket.Chat security patches addressing the markdown parsing issue.
6.0.0
- Ensure you have a complete backup of your Rocket.Chat installation and database before upgrading
- Review the official Rocket.Chat upgrade documentation for your current version
- Upgrade your Rocket.Chat server to version 6.0.0 or later
- After upgrading, verify the Search Messages functionality works correctly
- Test that the markdown parsing properly sanitizes input in the search feature
- Confirm your Content Security Policy is properly configured if you had it disabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28358 — 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-28358 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