CVE-2025-14644
BaseFortify
Publication date: 2025-12-14
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 |
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 exists in the itsourcecode Student Management System 1.0, specifically in an unknown function within the /update_subject.php file. By manipulating the argument ID, an attacker can perform SQL injection, which allows them to execute arbitrary SQL commands on the database remotely. The exploit has been publicly disclosed and can be used by attackers.
How can this vulnerability impact me? :
The vulnerability can allow remote attackers to perform SQL injection attacks, potentially leading to unauthorized access, modification, or deletion of data within the Student Management System's database. This can compromise the integrity, confidentiality, and availability of the system's data.
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 POST requests to the /update_subject.php file for SQL injection. One can use sqlmap with a command like: python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/update_subject.php" --data "id=1" --dbms=mysql --current-db. Additionally, testing with payloads such as boolean-based blind SQL injection, error-based SQL injection, or time-based blind SQL injection using the SLEEP function can help detect the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements and parameter binding to separate SQL code from user input, preventing injection. 2) Enforcing strict input validation and filtering on the 'id' parameter to ensure it conforms to expected numeric formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized attackers to perform SQL injection attacks that can lead to unauthorized access, data leakage, and data tampering. Such impacts on confidentiality, integrity, and availability of sensitive data can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate strict controls to protect personal and sensitive information. Therefore, exploitation of this vulnerability could lead to violations of these standards due to potential exposure or alteration of protected data. [1, 2]