Security readout for executives and security teams
Plain-English summary
Rocket.Chat versions before 0.66 could reflect unsafe content during account setup. A malicious link or registration interaction could cause script to run in a user's browser. The issue is old and source evidence does not show active exploitation, but externally reachable registration pages deserve review.
Executive priority
Treat as a moderate cleanup item unless an old Rocket.Chat instance still exposes registration publicly. Prioritize upgrade or retirement of vulnerable deployments because XSS can affect user sessions and trust, even when no active exploitation is documented.
Technical view
The CVE describes reflected XSS in Rocket.Chat's registration username step before 0.66. The attempted username was not saved with HTML control characters, but an error message displayed it unescaped through the listed username.js and username.html files.
Likely exposure
Exposure is likely limited to Rocket.Chat deployments before 0.66 where registration or account creation flows are reachable. Public self-registration would raise likelihood. The source bundle does not identify affected CPEs, hosted offerings, or downstream products.
Exploitation context
The source bundle does not indicate known active exploitation, and CISA KEV status is false. As reflected XSS, successful abuse would generally require a victim to interact with a crafted registration flow or link-like path that reaches the vulnerable error rendering.
Researcher notes
Evidence is sparse: CVE text and one GitHub issue support the vulnerable component and version boundary. No CVSS, CWE, exploit-in-the-wild report, or detailed patch advisory is included in the supplied bundle.
Mitigation direction
- Identify any Rocket.Chat deployments older than version 0.66.
- Upgrade affected Rocket.Chat instances to 0.66 or later.
- Restrict public registration if business use does not require it.
- Review vendor issue guidance before relying on compensating controls.
Validation and detection
- Confirm deployed Rocket.Chat version across production and staging.
- Check whether public account registration is enabled.
- Review registration username error handling for escaped output.
- Search historical logs for unusual registration error activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-13879 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/RocketChat/Rocket.Chat/issues/10795CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.