CVE-2025-14565
BaseFortify
Publication date: 2025-12-12
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'username' parameter in the /Profilers/SProfile/login1.php endpoint for SQL injection. You can use tools like sqlmap with commands such as: sqlmap -u "http://<target>/Profilers/SProfile/login1.php" --data="username=1&password=1" --dbs. Additionally, manual testing with payloads like 'username=3' AND 2202=2202 AND 'teRp'='teRp' (Boolean-based blind SQLi) or 'username=3' AND (SELECT 3355 FROM (SELECT(SLEEP(5)))XTbj) AND 'XdgI'='XdgI' (Time-based blind SQLi) can help detect the vulnerability. Also, Google dorking using inurl:Profilers/SProfile/login1.php can identify potentially vulnerable targets. [1, 2]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the kidaze CourseSelectionSystem, specifically in an unknown function within the file /Profilers/SProfile/login1.php. It occurs when the Username argument is manipulated, allowing an attacker to inject malicious SQL code. The attack can be performed remotely and an exploit is publicly available.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized access to sensitive data, data modification, or deletion. Since the attack can be performed remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system's data.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'username' parameter, minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits. Since no known mitigations or countermeasures have been published, replacing the affected component with an alternative product is also recommended. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized access, data leakage, and manipulation of sensitive data, it could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive information. Immediate remediation is recommended to protect data confidentiality, integrity, and availability, which are critical for compliance. [1, 2, 3]