CVE-2025-11033

7.3

kidaze · CourseSelectionSystem

The kidaze CourseSelectionSystem is vulnerable to remote SQL injection via the cbe argument in the /Profilers/PriProfile/COUNT3s7.php file, allowing unauthenticated attackers to manipulate database queries.

Executive summary

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

Vulnerability

The application fails to properly sanitize the cbe argument within the /Profilers/PriProfile/COUNT3s7.php file, resulting in SQL injection. This flaw can be triggered by an unauthenticated attacker remotely.

Business impact

Successful exploitation of this vulnerability allows unauthorized interaction with the underlying database, potentially leading to data exfiltration, unauthorized modification of records, or service disruption. With a CVSS score of 7.3, this represents a significant security risk that could facilitate further system compromise or administrative account takeover within the educational environment.

Remediation

Immediate Action: Since this product utilizes a rolling release model without specific versioned patches, users must monitor the official repository for updates and apply the latest commit immediately.

Proactive Monitoring: Security teams should monitor web server logs for suspicious HTTP requests targeting the /Profilers/PriProfile/COUNT3s7.php endpoint, specifically looking for SQL syntax patterns in the cbe parameter.

Compensating Controls: Implement a Web Application Firewall (WAF) with strict SQL injection protection rules to filter malicious input directed at the vulnerable endpoint until a permanent fix is integrated into the codebase.

Exploitation status

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the GitHub issue referenced by the vulnerability findings.

Analyst recommendation

Given the availability of a public proof-of-concept and the unauthenticated nature of the attack vector, this vulnerability poses a clear and present danger to affected systems. Administrators should prioritize identifying instances of this software and applying the latest available repository updates to negate the injection risk.

More kidaze CVEs

Sources

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