CVE-2022-50962
Reflected XSS in uBidAuction 2.0.1 Orders Module
Publication date: 2026-05-10
Last updated on: 2026-05-10
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ubidauction | ubidauction | 2.0.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-50962 is a reflected cross-site scripting (XSS) vulnerability found in uBidAuction version 2.0.1, specifically in the orders/myOrders module.
The vulnerability occurs because the parameters date_created, date_from, date_to, and created_at in the filter functionality are not properly sanitized.
This improper sanitization allows remote attackers to inject malicious scripts via crafted GET requests, which then execute in the browsers of victims.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute malicious scripts in the browsers of users who visit the affected site.
Such script execution can lead to theft of sensitive information, session hijacking, or other malicious actions performed on behalf of the victim.
Because the attack is reflected, it requires the victim to click on a crafted link or visit a specially crafted URL.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted GET requests to the orders/myOrders module, specifically targeting the parameters date_created, date_from, date_to, and created_at to check if they are properly sanitized.
For example, you can use curl commands to test for reflected XSS by injecting a simple script payload into these parameters and observing if the script is reflected in the response.
- curl -G 'http://<target>/orders/myOrders' --data-urlencode 'date_created=<script>alert(1)</script>'
- curl -G 'http://<target>/orders/myOrders' --data-urlencode 'date_from=<script>alert(1)</script>'
- curl -G 'http://<target>/orders/myOrders' --data-urlencode 'date_to=<script>alert(1)</script>'
- curl -G 'http://<target>/orders/myOrders' --data-urlencode 'created_at=<script>alert(1)</script>'
If the response contains the injected script without proper encoding or sanitization, it indicates the presence of the reflected XSS vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user-supplied input parameters such as date_created, date_from, date_to, and created_at in the orders/myOrders module.
Implement proper output encoding to prevent malicious scripts from being executed in the browser.
If possible, apply any available patches or updates from the vendor that address this vulnerability.
As a temporary measure, consider implementing web application firewall (WAF) rules to detect and block malicious payloads targeting these parameters.