A SQL injection vulnerability in thesystem version 1.0 allows attackers to bypass authentication and gain unauthorized access to user accounts.

The application fails to properly sanitize user input in the username parameter of the /check_users/ endpoint. This SQL injection flaw allows an attacker to manipulate backend database queries to bypass authentication mechanisms without requiring prior credentials.

The ability for an attacker to bypass authentication poses a significant risk to data confidentiality and integrity. Successful exploitation allows unauthorized individuals to access sensitive user account information stored within the database. Given the CVSS score of 7.1, this represents a high-severity risk that could lead to widespread account takeover and potential loss of administrative control over the application.

Immediate Action: Since no official patch is currently available, administrators should restrict access to the /check_users/ endpoint to trusted internal networks only.

Proactive Monitoring: Monitor web server access logs for anomalous POST requests to the /check_users/ endpoint containing SQL syntax characters such as single quotes or equality statements.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns targeting the username field.

Public Exploit Available: Yes, a functional exploit is available via the Exploit-DB entry 47432.

Due to the lack of an official vendor patch, users of thesystem version 1.0 must prioritize compensating controls to mitigate this high-risk vulnerability. Restricting network access to the application and implementing strict input filtering at the WAF level are essential steps to prevent unauthorized exploitation of this SQL injection flaw.