CVE-2025-6914
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 | student_record_system | 3.2 |
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-6914 is a critical SQL injection vulnerability in the PHPGurukul Student Record System version 3.2. It exists in the /edit-student.php file, specifically involving the 'fmarks2' parameter. This parameter is improperly sanitized and directly incorporated into SQL queries, allowing attackers to inject malicious SQL code. Exploiting this flaw enables attackers to manipulate SQL queries and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system compromise or service disruption. Attackers can manipulate SQL queries to alter, delete, or extract sensitive data, impacting the confidentiality, integrity, and availability of the system. [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 "fmarks2" parameter in the /edit-student.php file for SQL injection. Tools like sqlmap can be used to automate detection by targeting this parameter with SQL injection payloads, including time-based blind SQL injection techniques (e.g., using SLEEP commands). Additionally, Google dorking with the query "inurl:edit-student.php" can help identify potentially vulnerable targets. Example command using sqlmap: sqlmap -u "http://target/edit-student.php" --data="fmarks2=1" --technique=T --dbms=MySQL [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 by separating SQL code from user input. Enforce rigorous input validation and filtering to ensure inputs conform to expected formats. Additionally, minimize database user permissions by avoiding high-privilege accounts for routine operations to reduce potential damage from exploitation. If possible, consider replacing the affected product with a secure alternative. [2, 3]