CVE-2025-60239

8.5

Codexpert, Inc · CoSchool LMS

CoSchool LMS is vulnerable to Blind SQL Injection, which allows an authenticated attacker to execute unauthorized database queries by manipulating input parameters.

Executive summary

A Blind SQL Injection vulnerability in Codexpert CoSchool LMS allows authenticated attackers to extract sensitive database information, posing a high risk to data confidentiality.

Vulnerability

The application fails to properly neutralize special elements used in SQL commands, specifically within the CoSchool LMS plugin. This vulnerability requires the attacker to have at least low-level authenticated access to the system to trigger the blind SQL injection.

Business impact

Successful exploitation of this vulnerability allows an attacker to perform blind SQL injection, which can lead to the unauthorized extraction of sensitive data from the underlying database. Given the CVSS score of 8.5, this high-severity flaw threatens the confidentiality of student or user information stored within the LMS. Unauthorized data access can result in significant reputational damage, regulatory non-compliance, and loss of intellectual property.

Remediation

Immediate Action: Since no specific patch version is currently identified, administrators should monitor the vendor advisory for release updates and consider disabling the CoSchool LMS plugin if it is not business-critical.

Proactive Monitoring: Security teams should audit database logs for anomalous query patterns, such as unexpected time delays or excessive boolean-based error responses that are characteristic of blind SQL injection.

Compensating Controls: Deploy a Web Application Firewall with rules configured to detect and block common SQL injection payloads in HTTP requests directed at the plugin endpoints.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the high CVSS score and the potential for data exfiltration, this vulnerability represents a significant security risk. Administrators must prioritize the identification of the affected software within their environment and apply vendor-supplied updates as soon as they become available. Until a patch is released, restricting access to the affected module and implementing stringent WAF filtering is essential to mitigate the risk of unauthorized data exposure.

Sources

Originally found and disclosed by Martino Spagnuolo (r3verii) | Patchstack Bug Bounty Program, per the CVE Program record.