CVE-2023-50630
Description
TMS v2.28.0 has stored XSS via markdown payloads, allowing remote code execution in the chat page.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
TMS v2.28.0 has stored XSS via markdown payloads, allowing remote code execution in the chat page.
Vulnerability
A stored Cross-Site Scripting (XSS) vulnerability exists in xiweicheng TMS version v2.28.0. The flaw resides in the markdown rendering engine used across multiple pages, particularly in the chat page (/chat/@super). An attacker can inject arbitrary JavaScript by crafting a markdown link with a javascript: URI in the `click here` syntax. No special configuration is required beyond the application accepting and rendering user-supplied markdown content [1].
Exploitation
An attacker with network access to the TMS instance can send a crafted message containing the malicious markdown payload. The payload uses javascript:{onerror=eval}throw'=eval\x28String.fromCharCode\x28...\x29\x29') to execute arbitrary JavaScript code. For example, `click here triggers an alert(1)` in the victim's browser. The exploit vector is stored and triggers when any user views the chat page or similar markdown-rendered content [1].
Impact
Successful exploitation leads to arbitrary JavaScript execution in the context of the victim's browser, enabling session hijacking, credential theft, or further attacks such as Cross-Site Request Forgery (CSRF). The reference notes a potential chained attack where XSS could be used to change an administrator's password via the /admin/user/update2 endpoint without proper CSRF tokens [1]. The attacker gains the same privileges as the victim user, potentially escalating to full administrative control.
Mitigation
As of the available references, no official fix has been released by the vendor. The issue remains unpatched in v2.28.0. Suggested workarounds include replacing the markdown component with a safer alternative or implementing server-side filtering of XSS payloads before storing user input in the database [1]. Users should monitor the vendor's repository for updates and apply any security patches promptly.
AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2(expand)+ 1 more
- (no CPE)
- (no CPE)range: 2.28.0
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.