CVE-2025-6910
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-6910 is a critical SQL injection vulnerability in the PHPGurukul Student Record System version 3.2, specifically in the /session.php file. The vulnerability occurs because the 'session' parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries arbitrarily and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of 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 extract sensitive information, alter data, or disrupt the normal operation of the system. The attack can be performed remotely and easily due to publicly available proof-of-concept exploits. [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 "session" parameter in the /session.php file for SQL injection. One method is to perform a time-based blind SQL injection test using a payload such as: session=2025-2026' AND (SELECT 6293 FROM (SELECT(SLEEP(5)))fTjU)-- suWp. This can be done via a POST request to /studentrecordms/session.php. Tools like sqlmap can also be used to automate detection and enumeration of the vulnerability. Additionally, searching for URLs containing "session.php" may help identify vulnerable endpoints. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding use of elevated privilege accounts for routine operations. If possible, replacing the affected product with an alternative solution is recommended. These measures help protect system security and maintain data integrity. [2, 3]