CVE-2020-36931
Stored XSS in Click2Magic Chat Name Enables Admin Cookie Theft
Publication date: 2026-01-25
Last updated on: 2026-01-25
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| click2magic | click2magic | 1.1.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2020-36931 is a stored cross-site scripting (XSS) vulnerability in Click2Magic version 1.1.5. It allows attackers to inject malicious JavaScript code into the chat name input field. When an administrator later views or processes the chat containing this malicious input, the script executes in the administrator's browser, enabling the attacker to capture administrator cookies and potentially gain unauthorized access to sensitive information or user data. [1, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to steal administrator cookies through the injected malicious scripts. This can lead to unauthorized access to administrator accounts, compromising session security and potentially exposing sensitive user data or administrative functions within the Click2Magic application. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the chat name inputs for suspicious or malicious script payloads, such as injected JavaScript code. Specifically, look for chat names containing script tags or unusual HTML elements like: "<script src=https://.xss.ht></script>". Since the vulnerability involves stored cross-site scripting in the chat name input, you can search application logs or database entries for chat names containing script tags. Additionally, manual testing can be performed by attempting to input known XSS payloads into the chat name field and observing if the script executes when processed by an administrator. There are no specific commands provided, but searching logs or database entries for patterns like '<script' or 'javascript:' can help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs in the chat name field to prevent script injection. Implement proper input filtering to disallow HTML or JavaScript code in chat names. Additionally, apply security patches or updates from the vendor if available. As a temporary measure, restrict administrator access to the chat interface or avoid processing user requests containing untrusted chat names until a fix is applied. Educate administrators to be cautious when clicking on chat links or processing chat requests from untrusted users. [1, 3]