CVE-2026-5814
SQL Injection in PHPGurukul check_availability.php Enables Remote Exploit
Publication date: 2026-04-09
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 | online_course_registration | 3.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-5814 is a critical SQL injection vulnerability found in the PHPGurukul Online Course Registration 3.1 software, specifically in the /admin/check_availability.php file.
The vulnerability arises because the 'regno' parameter in POST requests is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code.
- The vulnerability can be exploited remotely without authentication.
- Attackers can use boolean-based blind or time-based blind SQL injection techniques.
Exploitation can lead to unauthorized database access, data leakage, modification or deletion of records, full system control, and service disruption.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including:
- Unauthorized access to sensitive database information.
- Leakage of confidential data.
- Modification or deletion of important records.
- Potential full control over the affected system by attackers.
- Disruption of services, affecting business continuity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "regno" POST parameter in the /admin/check_availability.php file for SQL injection flaws.
- Use boolean-based blind SQL injection payloads such as: regno=10806121' AND 7668=7668-- xbnX
- Use time-based blind SQL injection payloads such as: regno=10806121' AND (SELECT 3997 FROM (SELECT(SLEEP(5)))wcGy)-- SbCa
Tools like SQLMap can be used to automate detection by crafting POST requests targeting the regno parameter.
What immediate steps should I take to mitigate this vulnerability?
- Use prepared statements with parameter binding to separate SQL code from user input.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in PHPGurukul Online Course Registration 3.1 allows attackers to gain unauthorized access to the database, potentially leading to leakage, modification, or deletion of sensitive data. Such unauthorized data access and manipulation can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information against unauthorized access and breaches.
Failure to address this vulnerability could lead to exposure of personal data, violating confidentiality and integrity requirements under these standards, and may result in legal and financial consequences for organizations using the affected software.