CVE-2025-14578
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 |
|---|---|---|
| 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 Management System 1.0, specifically in an unknown function within the /update_account.php file. By manipulating the ID argument, an attacker can execute unauthorized SQL commands remotely, potentially compromising the database.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow an attacker to access, modify, or delete sensitive data within the student management system's database. This could lead to data breaches, loss of data integrity, and unauthorized access to user accounts or confidential information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability could lead to unauthorized access and exposure of personal or sensitive data, which may result in non-compliance with data protection regulations such as GDPR and HIPAA. Organizations affected by this vulnerability might face legal and regulatory consequences if the data breach occurs.
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 /update_account.php endpoint for SQL injection. Tools like sqlmap can be used to automate detection. Example sqlmap commands include targeting the vulnerable endpoint with the 'id' parameter via POST requests. Proof-of-concept payloads include boolean-based injections like `id=1' AND 1221=1221 AND 'Qdvt'='Qdvt` and time-based injections like `id=1' AND (SELECT 2990 FROM (SELECT(SLEEP(5)))hyey) AND 'pXxf'='pXxf`. Additionally, Google Dorking with queries such as `inurl:update_account.php` can help identify vulnerable targets. [1, 3]
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 (e.g., ensuring the 'id' parameter is numeric), and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Conducting regular security audits to detect and fix vulnerabilities promptly is also recommended. [1]