CVE-2025-14214
BaseFortify
Publication date: 2025-12-08
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 |
|---|---|---|
| itsourcecode | student_information_system | 1.0 |
| angeljudesuarez | student_management_system | 1.0 |
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
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the itsourcecode Student Information System 1.0, specifically in the /section_edit1.php file. An attacker can manipulate the ID argument to inject malicious SQL code. This can be exploited remotely and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection, which can lead to unauthorized access, data leakage, data modification, or disruption of the Student Information System. This can compromise the confidentiality, integrity, and availability of the system's data.
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 SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized database access, data tampering, and potential sensitive data leakage, it could negatively affect compliance by exposing personal or sensitive information, thereby violating data protection requirements. No direct statements about compliance impact are available in the provided texts. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /section_edit1.php file for SQL injection flaws. Since exploitation requires authentication and a valid session cookie, detection involves authenticated testing. You can use SQL injection payloads such as Boolean-based blind injection (e.g., id=" OR NOT 6946=6946#"), error-based injection, or time-based blind injection payloads to test the parameter. Additionally, attackers may be identified by monitoring for unusual SQL query patterns or by using Google dorking with the query inurl:section_edit1.php to find vulnerable endpoints. Specific commands for testing include sending POST requests with malicious 'id' values using tools like curl or sqlmap with authentication cookies. For example, using curl: curl -X POST -d "id=' OR NOT 6946=6946#" -b "PHPSESSID=your_session_id" https://target/section_edit1.php [2, 3]
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 by separating SQL code from user input. 2) Enforce strict input validation and filtering to ensure the 'id' parameter only accepts expected formats, such as numeric values. 3) Minimize database user permissions to avoid using high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product. These measures help prevent exploitation and reduce the risk posed by this vulnerability. [1, 2, 3]