CVE-2026-5635
SQL Injection in PHPGurukul /categorywise-products.php Allows Remote Attack
Publication date: 2026-04-06
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_shopping_portal_project | 2.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-5635 is an SQL injection vulnerability found in the PHPGurukul Online Shopping Portal Project version 2.1, specifically in the /categorywise-products.php file. The issue arises because the 'cid' parameter in the URL is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely.
- The vulnerable parameter is 'cid' in a GET request.
- Attack types include Boolean-based blind SQL injection, time-based blind SQL injection using MySQL SLEEP function, and UNION-based SQL injection to extract data.
Exploitation can lead to unauthorized database access, data leakage, data manipulation, full system compromise, and potential service disruption.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to your database, leakage of sensitive data, manipulation or deletion of data, full compromise of the affected system, and disruption of services.
Attackers can exploit the flaw remotely by injecting malicious SQL commands through the vulnerable 'cid' parameter, potentially gaining control over the backend database and the application.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the 'cid' GET parameter in the /categorywise-products.php file for SQL injection flaws.
- Use Boolean-based blind SQL injection payloads such as: cid=3' AND 4107=4107--
- Use Time-based blind SQL injection payloads with MySQL SLEEP function, for example: cid=3' AND (SELECT 1188 FROM (SELECT(SLEEP(5)))tRcq)--
- Use UNION-based SQL injection payloads to extract data, e.g.: cid=3' UNION ALL SELECT NULL,CONCAT(0x716b7a6b71,0x4b4244504f64757a794a694747559674b51507470504f556c7655594d5061515a56735655626644,0x716a6b7171),NULL,NULL,NULL--
Tools like sqlmap can be used to automate detection by crafting HTTP GET requests targeting the vulnerable parameter.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- 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 for routine operations.
Taking these corrective actions is critical to protect system security and maintain data integrity.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the PHPGurukul Online Shopping Portal Project 2.1 allows unauthorized database access, data leakage, and data manipulation. Such impacts can lead to breaches of sensitive personal or health information, which would negatively affect compliance with common standards and regulations like GDPR and HIPAA that require protection of data confidentiality and integrity.
Failure to remediate this vulnerability could result in unauthorized disclosure or alteration of protected data, potentially causing violations of data protection laws and resulting in legal and financial penalties.