CVE-2025-14209
BaseFortify
Publication date: 2025-12-08
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 |
|---|---|---|
| campcodes | school_file_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows attackers to gain unauthorized access to sensitive data, modify or delete records, and take control of the system. Such unauthorized access and potential data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. Therefore, exploitation of this vulnerability could result in violations of these standards due to compromised data confidentiality, integrity, and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by sending specially crafted payloads to the /update_query.php endpoint, particularly manipulating the stud_id POST parameter. For example, boolean-based blind SQL injection can be tested using payloads with the RLIKE operator, and time-based blind SQL injection can be tested using payloads with the SLEEP() function to observe response delays. Tools like sqlmap can automate this detection. Example commands include using sqlmap with parameters such as stud_no=12345 and stud_id=1' AND (SELECT SLEEP(5))-- to verify if the system is vulnerable. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. [1]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection weakness in the Campcodes School File Management System 1.0, specifically in the /update_query.php file. An attacker can manipulate the stud_id parameter remotely to execute unauthorized SQL commands on the database.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to access, modify, or delete sensitive data stored in the database, potentially leading to data breaches, loss of data integrity, and disruption of the system's normal operations.