CVE-2025-11089
BaseFortify
Publication date: 2025-09-28
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kidaze | courseselectionsystem | to 2017-06-18 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11089 is a critical SQL injection vulnerability in the kidaze CourseSelectionSystem, specifically in the file /Profilers/PriProfile/COUNT3s4.php. It occurs because the 'cbranch' argument is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw can be exploited remotely without authentication, enabling attackers to manipulate the database by executing unauthorized SQL commands. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, modification or deletion of data, and potentially full system control. It can also cause service disruption. Since exploitation requires no authentication and can be done remotely, it poses a significant risk to the confidentiality, integrity, and availability of the system and its data. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'cbranch' parameter in the URL /Profilers/PriProfile/COUNT3s4.php for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/Profilers/PriProfile/COUNT3s4.php" --data="cbranch=1" --risk=3 --level=5 --batch. Additionally, manual testing with payloads such as "cbranch=1' OR NOT 7621=7621 #" (Boolean-based blind SQLi) or "cbranch=1' AND (SELECT SLEEP(5))--" (time-based blind SQLi) can be used to confirm the vulnerability. Vulnerable targets can also be identified using Google dorking with the query: inurl:Profilers/PriProfile/COUNT3s4.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Apply strict input validation and filtering on the 'cbranch' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. Since no specific patches are available due to rolling releases, consider replacing the vulnerable product with an alternative if possible. [1, 2, 3]