Skip to main content

CVE-2025-11089: SQL Injection in kidaze CourseSelectionSystem

Medium
VulnerabilityCVE-2025-11089cvecve-2025-11089
Published: Sun Sep 28 2025 (09/28/2025, 00:02:05 UTC)
Source: CVE Database V5
Vendor/Project: kidaze
Product: CourseSelectionSystem

Description

A vulnerability was determined in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. This impacts an unknown function of the file /Profilers/PriProfile/COUNT3s4.php. Executing manipulation of the argument cbranch can lead to sql injection. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

AI-Powered Analysis

AILast updated: 09/28/2025, 00:33:20 UTC

Technical Analysis

CVE-2025-11089 is a SQL Injection vulnerability identified in the kidaze CourseSelectionSystem, specifically affecting an unknown function within the file /Profilers/PriProfile/COUNT3s4.php. The vulnerability arises from improper sanitization or validation of the 'cbranch' argument, which can be manipulated by an attacker to inject malicious SQL code. This injection flaw allows remote attackers to execute arbitrary SQL commands on the backend database without requiring any authentication or user interaction. The product uses a rolling release model, making exact versioning details ambiguous, but the affected version is identified by the commit hash 42cd892b40a18d50bd4ed1905fa89f939173a464. The vulnerability has been publicly disclosed, but no confirmed exploits in the wild have been reported yet. The CVSS v4.0 base score is 6.9, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges or user interaction required (PR:N/UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L/VI:L/VA:L). The vulnerability does not require any special conditions such as scope changes or security requirements. The lack of patch links suggests that a fix may not yet be publicly available or is pending due to the continuous delivery model of the software. Given the nature of SQL Injection, successful exploitation could lead to unauthorized data access, data modification, or disruption of service within the CourseSelectionSystem environment.

Potential Impact

For European organizations, especially educational institutions or entities using the kidaze CourseSelectionSystem for managing course selections, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to sensitive student data, including personal information, academic records, and enrollment details, potentially violating GDPR and other data protection regulations. Data integrity could be compromised, leading to incorrect course registrations or manipulation of academic records. Availability impacts could disrupt course selection processes during critical enrollment periods, affecting operational continuity. Furthermore, the exposure of such vulnerabilities could damage institutional reputation and erode trust among students and staff. The remote and unauthenticated nature of the attack increases the likelihood of exploitation, especially if the system is accessible over the internet or poorly segmented networks. The medium severity rating suggests that while the vulnerability is serious, it may not lead to full system compromise without additional factors, but the risk remains substantial given the sensitivity of the data involved.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Immediate code review and input validation: Sanitize and validate the 'cbranch' parameter rigorously to prevent injection of malicious SQL code. Employ parameterized queries or prepared statements to eliminate direct concatenation of user input into SQL commands. 2) Network segmentation and access controls: Restrict external access to the CourseSelectionSystem backend, ensuring it is only accessible within trusted internal networks or via secure VPNs. 3) Web Application Firewall (WAF): Deploy and configure a WAF with rules specifically designed to detect and block SQL Injection attempts targeting the vulnerable parameter. 4) Monitoring and logging: Enhance logging around the vulnerable endpoint to detect anomalous query patterns or repeated access attempts that may indicate exploitation attempts. 5) Patch management: Engage with the vendor or development team to obtain or expedite a security patch addressing this vulnerability, given the rolling release model. 6) Incident response preparedness: Develop and test incident response plans specific to data breaches or service disruptions stemming from SQL Injection attacks. 7) Regular security assessments: Conduct penetration testing and code audits focusing on injection flaws and other input validation issues to proactively identify and remediate vulnerabilities.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-27T05:21:05.899Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68d87ec65d6228f86ddcb334

Added to database: 9/28/2025, 12:18:14 AM

Last enriched: 9/28/2025, 12:33:20 AM

Last updated: 9/28/2025, 1:03:14 AM

Views: 2

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats