{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-13878 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-13878 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-13878 is a medium-severity cross-site scripting vulnerability in Rocket.chat Rocket.chat, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-13878 and fix it if it is affected.\n\nWhat it is: CVE-2018-13878 is a medium-severity cross-site scripting vulnerability in Rocket.chat Rocket.chat, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-13878 in the wild and no public exploit code.\n\nAffected product: Rocket.chat Rocket.chat. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-13878/ (Markdown: https://insights.sbomify.com/CVE-2018-13878/index.md)","id":"CVE-2018-13878","markdown":"https://insights.sbomify.com/CVE-2018-13878/index.md","name":"CVE-2018-13878","record":{"aliases":["GHSA-8f7m-2hjp-gccx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Rocket.Chat","requires_auth":"none","summary":"Attackers can execute scripts via unescaped usernames in mentions, potentially stealing secret tokens from users and admins.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rocket.chat","vendor":"rocket.chat"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"An XSS issue was discovered in packages/rocketchat-mentions/Mentions.js in Rocket.Chat before 0.65. The real name of a username is displayed unescaped when the user is mentioned (using the @ symbol) in a channel or private chat. Consequently, it is possible to exfiltrate the secret token of every user and also admins in the channel.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2018-13878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"rocket.chat:rocket.chat","products":["rocket.chat:rocket.chat"],"type":"xss","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-13879"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-13877"},"products":["n/a"],"published":"2018-07-11","related":[{"cvss_score":9.8,"headline":"Auth bypass in Rocket.Chat","id":"CVE-2026-58066","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":9.8,"headline":"SQL injection in Rocket.Chat","id":"CVE-2026-29198","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":9.8,"headline":"Security feature bypass in Rocket.Chat","id":"CVE-2023-28316","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":9.8,"headline":"Command injection in Rocket.chat - Electron Desktop","id":"CVE-2022-44567","kev_date_added":null,"published":"2022-12-23"},{"cvss_score":9.8,"headline":"Code injection in Rocket.Chat server","id":"CVE-2021-22910","kev_date_added":null,"published":"2021-08-09"},{"cvss_score":9.8,"headline":"Code injection in Rocket.Chat server","id":"CVE-2021-22911","kev_date_added":null,"published":"2021-05-27"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-29594","kev_date_added":null,"published":"2020-12-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can execute scripts via unescaped usernames in mentions, potentially stealing secret tokens from users and admins.","url":"https://insights.sbomify.com/CVE-2018-13878/"}