CVE-2025-15220
Cross-Site Scripting in SohuTV CacheCloud LoginController
Publication date: 2025-12-30
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sohutv | cachecloud | 3.2.0 |
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. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a cross-site scripting (XSS) issue found in the init function of the LoginController.java file in SohuTV CacheCloud up to version 3.2.0. It allows an attacker to inject malicious scripts remotely, potentially compromising the security of users interacting with the affected application.
How can this vulnerability impact me? :
The vulnerability can lead to cross-site scripting attacks, which may allow attackers to execute malicious scripts in the context of the affected application. This can result in unauthorized actions performed on behalf of users, theft of session tokens, or other malicious activities that compromise user security and trust.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /manage/login endpoint of SohuTV CacheCloud (up to version 3.2.0) for reflected Cross-Site Scripting (XSS) by injecting a script payload into the 'redirectUrl' parameter and observing if it is reflected unsanitized in the response. A practical approach is to send a crafted HTTP GET request with a malicious script in the 'redirectUrl' parameter and check if the script appears in the response HTML. For example, using curl: curl -v 'http://<target>/manage/login?redirectUrl=%22%3E%3Cscript%3Ealert(1)%3C/script%3E' and inspecting the response for the injected script tag. Alternatively, automated scanners or custom scripts (such as the Python PoC using requests library) can be used to verify the vulnerability by sending similar payloads and analyzing the response. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Avoid using or exposing the vulnerable /manage/login endpoint until a fix is available. 2) Implement input validation and output encoding on the 'redirectUrl' parameter to neutralize malicious scripts before rendering. 3) If possible, replace or upgrade the affected software component, as no vendor patch or official mitigation currently exists. 4) Employ web application firewalls (WAF) to detect and block malicious payloads targeting this XSS vulnerability. 5) Educate users about the risk of interacting with suspicious links that may exploit this vulnerability. [1, 3]