LogicalDOC Enterprise contains a high-severity SQL injection vulnerability that allows authenticated attackers to execute unauthorized database queries and potentially compromise system data.

The application is susceptible to a blind SQL injection vulnerability within the ComparisonServlet component. The attack requires the user to be authenticated, at which point they can inject malicious SQL commands into the application backend.

A successful exploit of this vulnerability could lead to unauthorized access, modification, or deletion of sensitive information stored within the database. Given the CVSS score of 8.8, this flaw represents a significant risk to data integrity and confidentiality. Organizations relying on LogicalDOC for document management face potential operational disruption and the risk of unauthorized data exposure if an attacker gains access to a user account.

Immediate Action: Contact LogicalDOC support or monitor the official vendor security portal for the release of a security patch addressing the ComparisonServlet vulnerability. Until a patch is released, restrict access to the application to only necessary personnel to minimize the risk of exploitation by compromised accounts.

Proactive Monitoring: Review web server and application logs for anomalous patterns in HTTP requests directed at the ComparisonServlet, specifically looking for SQL keywords or unusual character sequences.

Compensating Controls: Deploy a Web Application Firewall (WAF) with custom rules designed to detect and block SQL injection payloads targeting servlet parameters.

Public Exploit Available: Yes, a public proof-of-concept is available via the referenced GitHub disclosure.

Due to the high severity of this SQL injection flaw and the existence of public exploit material, immediate attention is required. Administrators should prioritize identifying all instances of LogicalDOC Enterprise within their environment and prepare to apply security updates as soon as they are made available by the vendor.