CVE-2025-6913
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-6913 is a critical SQL injection vulnerability in the PHPGurukul Student Record System version 3.2, specifically in the /admin-profile.php file. It occurs due to improper sanitization and validation of the 'aemailid' parameter, which is directly used in SQL queries without proper neutralization. This allows attackers to inject malicious SQL code remotely, potentially leading to unauthorized database access, data leakage, data tampering, full system control, and service disruption. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker can remotely exploit the flaw to access sensitive data, modify or delete information, gain full control over the system, and disrupt services. The attack is easy to execute and can lead to significant security breaches and operational downtime. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "aemailid" parameter in the /admin-profile.php file for SQL injection. Tools like sqlmap can be used to automate detection. An example command using sqlmap is: sqlmap -u "http://targetsite/admin-profile.php" --data="adminname=admin&aemailid=admin123%40gmail.com&submit=Update+Profile" -p aemailid --batch Additionally, Google dorking can help identify vulnerable targets using the query: inurl:admin-profile.php [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Use prepared statements with parameter binding to prevent SQL injection. - Implement strict input validation and filtering on the "aemailid" parameter. - Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. - Consider replacing the affected product with an alternative solution if possible. [1, 2]