CVE-2025-14639
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 file /uprec.php. It allows an attacker to perform SQL injection by manipulating the argument ID. This means that an attacker can inject malicious SQL code remotely to interfere with the database operations of the system.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely execute SQL injection attacks, potentially leading to unauthorized access, data leakage, data modification, or disruption of the 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 the /uprec.php file for SQL injection. One suggested command is using the sqlmap tool to automate detection: python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/uprec.php" --data "id=1" --dbms=mysql --current-db. Additionally, a proof-of-concept payload for manual testing is: id=1' AND (SELECT 6486 FROM (SELECT(SLEEP(5)))sigx) AND 'XEPs'='XEPs, which causes a delay if the injection is successful. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements and parameter binding to separate SQL code from user input, enforcing strict input validation and filtering (e.g., ensuring 'id' is numeric), minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits to detect and address vulnerabilities promptly. [1]