CVE-2023-50866: Kashipara Group Travel Website · SQL Injection
Affects Kashipara Group Travel WebsiteSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Kashipara Group Travel Website | Affected
| Fixed in– |
AI-suggested
First, deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL Injection attempts targeting the 'username' parameter in loginAction.php. Input validation and sanitization should be enforced at the application layer by implementing strict whitelisting of allowed characters for the username field, such as alphanumeric characters only. Organizations should also consider temporarily disabling or restricting access to the vulnerable login endpoint if feasible. Conduct thorough logging and monitoring of all login attempts to detect anomalous patterns indicative of exploitation attempts. Network segmentation should be applied to isolate the database server from direct internet access, reducing exposure. Finally, organizations should engage with the vendor to request a security patch and plan for an urgent update once available. Regular security assessments and penetration testing focusing on injection flaws are recommended to prevent similar vulnerabilities.
Description
Travel Website v1.0 is vulnerable to multiple Unauthenticated SQL Injection vulnerabilities. The 'username' parameter of the loginAction.php resource does not validate the characters received and they are sent unfiltered to the database.