CVE-2025-10597

7.3

kidaze · CourseSelectionSystem

The kidaze CourseSelectionSystem is vulnerable to remote SQL injection via the cname argument in the /Profilers/PriProfile/COUNT2.php file.

Executive summary

A critical SQL injection vulnerability in the kidaze CourseSelectionSystem allows unauthenticated remote attackers to manipulate database queries.

Vulnerability

This vulnerability is a SQL injection flaw (CWE-89) triggered by improper input validation of the cname parameter within the /Profilers/PriProfile/COUNT2.php script. The attack vector is network-based and requires no authentication from the attacker.

Business impact

Successful exploitation of this vulnerability can lead to unauthorized database access, potential data exposure, or modification of sensitive course selection information. Given the CVSS score of 7.3, this represents a high-severity risk that could compromise the integrity and confidentiality of the application backend.

Remediation

Immediate Action: As no specific patch version is available due to the rolling release model of the software, administrators should restrict access to the vulnerable /Profilers/PriProfile/COUNT2.php file or implement strict input validation on the cname parameter.

Proactive Monitoring: Monitor server access logs for suspicious patterns in HTTP requests directed at the /Profilers/PriProfile/ directory, specifically looking for encoded SQL syntax or unusual string length in the cname parameter.

Compensating Controls: Deploy a Web Application Firewall (WAF) rule to identify and block SQL injection attempts targeting the affected endpoint.

Exploitation status

Public Exploit Available: No (There is no confirmed weaponized exploit, though a proof-of-concept exists as referenced in the vulnerability data).

Analyst recommendation

Due to the unauthenticated nature of this SQL injection vulnerability, the risk to the CourseSelectionSystem is significant. Organizations should prioritize implementing WAF filtering and restricting access to the affected script immediately, as the lack of a formal versioned patch necessitates defensive configuration changes to protect the database environment.

More kidaze CVEs

Sources

Originally found and disclosed by shang (VulDB User), per the CVE Program record.