CVE-2025-14588
BaseFortify
Publication date: 2025-12-13
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 flaw in the itsourcecode Student Management System 1.0, specifically in the /update_program.php file. By manipulating the 'ID' argument, an attacker can inject malicious SQL code. The attack can be performed remotely, and an exploit has already been publicly released.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /update_program.php endpoint for SQL injection on the 'id' parameter. One common approach is to use sqlmap, an automated SQL injection tool, with a command targeting the vulnerable parameter, for example: sqlmap -u "http://target/update_program.php" --data="id=1" --risk=3 --level=5. Additionally, searching for the vulnerable endpoint using Google dorking with the query "inurl:update_program.php" can help identify exposed targets. Monitoring network traffic for suspicious requests manipulating the 'id' parameter may also help detect exploitation attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, applying strict input validation and filtering to ensure the 'id' parameter only accepts expected formats (such as numeric values), and minimizing database user permissions to restrict access rights, avoiding the use of high-privilege accounts for routine operations. Regular security audits should be conducted to detect and remediate vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended, as no known countermeasures have been documented. [2, 3]
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. This can compromise the confidentiality, integrity, and availability of the system's data.