CVE-2020-37163
SQL Injection in QuickDate 1.3.2 Enables Data Extraction
Publication date: 2026-02-07
Last updated on: 2026-02-07
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| quickdate | quickdate | 1.3.2 |
| quickdate | quickdate | to 1.3.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2020-37163 is a SQL injection vulnerability found in QuickDate version 1.3.2. It occurs in the 'find_matches' endpoint through the '_located' parameter. Attackers can manipulate this parameter to inject UNION-based SQL statements, which allows them to extract sensitive information from the database."}, {'type': 'paragraph', 'content': "Specifically, the injection enables attackers to retrieve data such as database user credentials, the database name, and the system version. This is done by concatenating these pieces of information using SQL functions and receiving them in the server's response."}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive database information, including user credentials. An attacker exploiting this flaw can gain insights into the database structure and contents, potentially leading to further attacks or data breaches.
The CVSS v4.0 score of 8.8 indicates a high severity, with the vulnerability exploitable remotely over the network without any privileges or user interaction. The confidentiality impact is high, meaning sensitive data can be exposed, while integrity and availability impacts are low or none.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability in QuickDate 1.3.2 can be detected by sending crafted POST requests to the /find_matches endpoint, specifically manipulating the '_located' parameter with UNION-based SQL payloads."}, {'type': 'paragraph', 'content': 'For example, a test command using curl might look like this:'}, {'type': 'list_item', 'content': "curl -X POST 'http://targetsite/find_matches' -d '_located=1 UNION ALL SELECT NULL, CONCAT_WS(0x3a, user(), database(), @@version), NULL-- ' -H 'Content-Type: application/x-www-form-urlencoded' -H 'Cookie: your_session_cookie'"}, {'type': 'paragraph', 'content': 'If the server responds with database user, database name, and version information in the JSON response, it confirms the presence of the vulnerability.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include:'}, {'type': 'list_item', 'content': "Apply input validation and sanitization on the '_located' parameter to prevent SQL injection."}, {'type': 'list_item', 'content': 'Use prepared statements or parameterized queries in the application code to handle database queries safely.'}, {'type': 'list_item', 'content': 'Restrict or monitor access to the /find_matches endpoint, especially for unauthenticated or suspicious users.'}, {'type': 'list_item', 'content': 'If possible, update QuickDate to a version where this vulnerability is fixed.'}, {'type': 'list_item', 'content': 'Monitor logs for unusual SQL syntax or unexpected database errors that could indicate exploitation attempts.'}] [1, 2]