CVE-2025-6318
BaseFortify
Publication date: 2025-06-20
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 | pre-school_enrollment_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
Can you explain this vulnerability to me?
CVE-2025-6318 is a critical SQL injection vulnerability in the PHPGurukul Pre-School Enrollment System version 1.0. It exists in the /admin/check_availability.php file, where the 'username' parameter is directly used in SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code remotely, manipulating the database queries to perform unauthorized actions such as data leakage or modification. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data manipulation, and potentially full system compromise or service disruption. The attack can be performed remotely without any authentication, making it easier for attackers to exploit. This can result in loss of confidentiality, integrity, and availability of the affected 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 "username" parameter in the /admin/check_availability.php endpoint for SQL injection. Tools like sqlmap can be used to automate detection by targeting this parameter. Example sqlmap command: sqlmap -u "http://target/admin/check_availability.php" --data="username=admin" -p username --technique=BEUSTQ. Additionally, manual testing can be done using payloads such as boolean-based: username=admin' AND 7648=7648-- GLZX or time-based: username=admin' AND (SELECT 1287 FROM (SELECT(SLEEP(5)))kIkw)-- YnIP to observe responses or delays indicating SQL injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the "username" parameter, and restricting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine database operations. If possible, replace the affected component with an alternative product. Prompt corrective action is critical to protect system security and data integrity. [2, 3]