CVE-2025-14334
BaseFortify
Publication date: 2025-12-09
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 |
|---|---|---|
| angeljudesuarez | student_management_system | 1.0 |
| itsourcecode | 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 flaw in the itsourcecode Student Management System 1.0, specifically in an unknown function within the /new_adviser.php file. By manipulating the 'Name' argument, an attacker can execute unauthorized SQL commands remotely.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform SQL injection attacks remotely, potentially leading to unauthorized access, data leakage, data modification, or disruption of the Student Management System's database.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and potential leakage of sensitive data due to SQL injection, which can lead to violations of data protection standards such as GDPR and HIPAA. Exploitation can compromise confidentiality, integrity, and availability of personal and sensitive information, thereby impacting compliance with these regulations. Immediate remediation is necessary to protect data integrity and maintain compliance. [1, 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 'name' POST parameter in the /new_adviser.php file for SQL injection. You can use tools like sqlmap targeting the 'name' parameter with crafted payloads such as boolean-based blind, error-based, or time-based SQL injection techniques. Example sqlmap command: sqlmap -u http://target/new_adviser.php --data="name=1" --risk=3 --level=5 --technique=BEUST --dbms=MySQL. Additionally, Google Dorking with the query inurl:new_adviser.php can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include using prepared statements with parameter binding to separate SQL code from user input, implementing strict input validation and filtering on the 'name' parameter, minimizing database user permissions to avoid high-privilege accounts for routine operations, and conducting regular security audits to detect and remediate vulnerabilities promptly. [1]