CVE-2025-6888
BaseFortify
Publication date: 2025-06-30
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 |
|---|---|---|
| phpgurukul | teachers_record_management_system | 2.1 |
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
Can you explain this vulnerability to me?
CVE-2025-6888 is a critical SQL injection vulnerability in the PHPGurukul Teachers Record Management System version 2.1, specifically in the /admin/changeimage.php file. The vulnerability arises because the 'tid' parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data manipulation, and full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without authentication. This can lead to unauthorized access to sensitive data, modification or deletion of data, exposure of confidential information, and potentially full compromise of the system. The integrity, confidentiality, and availability of your system can be compromised. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'tid' parameter in the /admin/changeimage.php endpoint for SQL injection. Example commands include using curl or a browser to send crafted GET requests such as: - Boolean-based blind SQL injection test: curl 'http://target/trms/admin/changeimage.php?tid=2 AND 8322=8322' - Time-based blind SQL injection test: curl 'http://target/trms/admin/changeimage.php?tid=2 AND (SELECT 6421 FROM (SELECT(SLEEP(5)))GjOu)' - Using sqlmap tool to automate detection and exploitation: sqlmap -u 'http://target/trms/admin/changeimage.php?tid=2' --batch These tests check if the 'tid' parameter is vulnerable to SQL injection by observing responses or delays caused by injected payloads. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Enforce strict input validation and filtering on the 'tid' parameter to ensure it conforms to expected formats. - Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. These measures help prevent SQL injection attacks by ensuring user inputs cannot alter SQL queries maliciously. [1, 3]