uBidAuction 2.0.1 contains a reflected cross-site scripting vulnerability in the auctions/myAuctions/status/loose module. The date_created, date_from, date_to, and created_at parameters in the filter functionality are not properly sanitized, allowing remote attackers to inject malicious scripts via crafted GET requests that execute in victims' browsers.
Security readout for executives and security teams
Plain-English summary
This is a reflected cross-site scripting issue in uBidAuction 2.0.1. An attacker could trick a user into opening a crafted auction filter link, causing script to run in that user's browser. The likely business impact is account-session abuse, phishing, or misleading content, not server takeover.
Executive priority
Treat as a moderate web application risk. Prioritize if uBidAuction 2.0.1 is public-facing or used by authenticated customers, because successful abuse depends on user interaction but can affect trust and sessions.
Technical view
CVE-2022-50964 affects the auctions/myAuctions/status/loose filter path in uBidAuction 2.0.1. The date_created, date_from, date_to, and created_at GET parameters are not properly sanitized, enabling reflected XSS. CVSS 3.1 is 6.1: network reachable, low complexity, no privileges, user interaction required, changed scope.
Likely exposure
Exposure appears limited to organizations running uBidAuction 2.0.1, especially if auction account pages are internet-accessible. The source bundle does not claim other versions are affected and provides no CPE data.
Exploitation context
Public exploit/advisory references exist from Exploit-DB and Vulnerability Lab. The bundle marks CISA KEV as false and provides no cited evidence of active exploitation in the wild.
Researcher notes
Evidence names a reflected XSS sink and specific parameters but does not include a vendor patch version, CPEs, or active exploitation confirmation. Avoid assuming broader product impact beyond uBidAuction 2.0.1.
Mitigation direction
Identify whether uBidAuction 2.0.1 is deployed anywhere.
Check vendor or maintainer guidance for an official fixed release.
Sanitize and output-encode the named filter parameters server-side.
Restrict access to affected auction account pages where feasible.
Use WAF rules only as temporary compensating control.
Validation and detection
Inventory public and internal sites for uBidAuction 2.0.1.
Review logs for requests to auctions/myAuctions/status/loose with unusual filter values.
Confirm affected parameters are safely encoded in a staging environment.
Retest after remediation to verify scripts render inertly.
Document any exposed instances and owner remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.