CVE-2025-11052
BaseFortify
Publication date: 2025-09-27
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 | * |
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-11052 is a critical SQL injection vulnerability in the kidaze CourseSelectionSystem version 1.0, specifically in the file /Profilers/PriProfile/COUNT3s5.php. The vulnerability occurs because the 'csslc' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database queries to access, modify, or delete data unauthorizedly. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, tampering or deletion of data, full system control by attackers, and potential service disruptions. Since exploitation requires no authentication and can be done remotely, it poses a high risk to system confidentiality, integrity, and availability. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'csslc' parameter in the /Profilers/PriProfile/COUNT3s5.php file for SQL injection flaws. You can use SQL injection testing tools such as sqlmap to automate detection. Example payloads include boolean-based blind SQL injection: csslc=1' OR NOT 4168=4168 # &s5= and time-based blind SQL injection: csslc=1' AND (SELECT 7100 FROM (SELECT(SLEEP(5)))ySmH)-- QODw&s5=. Additionally, attackers may identify vulnerable targets using Google dorking with the query: inurl:Profilers/PriProfile/COUNT3s5.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and address vulnerabilities promptly. If possible, consider replacing the affected component with an alternative product. [1, 2]