CVE-2022-50896
Reflected XSS in Testa 3.5.1 login.php Redirect Parameter
Publication date: 2026-01-13
Last updated on: 2026-01-13
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| testa | testa | 3.5.1 |
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-2022-50896 is a reflected cross-site scripting (XSS) vulnerability in Testa version 3.5.1. It occurs in the login.php page's redirect parameter, where attackers can inject malicious JavaScript code by crafting a specially encoded payload. When a victim accesses a URL containing this payload, the malicious script executes in their browser context. [2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary JavaScript in the victim's browser, potentially leading to session hijacking, theft of sensitive information, or other client-side attacks. Exploitation requires user interaction but no special privileges or authentication. [3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the login.php page's redirect parameter for reflected XSS. You can craft a URL with a payload such as: https://yourserver/login.php?redirect=%22%3E%3Cscript%3Ealert(%22XSS%22)%3C/script%3E and observe if an alert box appears in the browser, indicating script execution. Automated scanning tools that detect reflected XSS vulnerabilities can also be used. There are no specific network commands provided, but manual testing with crafted URLs as described is effective. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating the input for the redirect parameter in login.php to prevent script injection. Applying patches or updates from the vendor if available is recommended. As a temporary workaround, you can disable or restrict the use of the redirect parameter or implement a whitelist of allowed redirect URLs. Additionally, educating users to avoid clicking suspicious links can reduce exploitation risk. [3]