A critical SQL injection vulnerability in QuickDate 1.3.2 allows unauthenticated remote attackers to extract sensitive database information, including user credentials.

The application fails to properly sanitize the _located parameter within the find_matches endpoint. An unauthenticated attacker can supply a crafted UNION-based SQL statement to execute arbitrary queries against the backend database.

Successful exploitation of this flaw poses a severe risk to data confidentiality and integrity. By leveraging this SQL injection, an attacker can extract sensitive information such as user credentials, database names, and system versions, potentially leading to a complete compromise of the application data. With a CVSS score of 8.2, this vulnerability is considered high severity and requires immediate attention to prevent unauthorized data exfiltration.

Immediate Action: Update the QuickDate installation to a version that incorporates a patch for this SQL injection vulnerability. If a patch is unavailable, restrict access to the find_matches endpoint at the network or application level.

Proactive Monitoring: Monitor web server logs for suspicious POST requests to the /find_matches endpoint, specifically looking for SQL syntax patterns or unexpected character strings in the _located parameter.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection payloads targeting the application input parameters.

Public Exploit Available: Yes, a functional proof-of-concept exists and is documented in the Exploit-DB entry 48022.

Given the availability of a functional exploit and the high CVSS score, organizations running QuickDate 1.3.2 must prioritize remediation. Organizations should verify if they are on an affected version and apply the necessary updates provided by the vendor immediately to mitigate the risk of data compromise. If immediate patching is not feasible, implement strict WAF filtering to block malicious requests targeting the vulnerable endpoint.