CVE-2026-5552
SQL Injection in PHPGurukul /sub-category.php Enables Remote Attack
Publication date: 2026-04-05
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 | to 2.1 (inc) |
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-5552 is a critical SQL injection vulnerability found in the PHPGurukul Online Shopping Portal Project version 2.1, specifically in the /sub-category.php file. The issue arises from improper handling of the 'pid' parameter, which is directly used in SQL queries without proper sanitization or validation.
This flaw allows attackers to inject malicious SQL code, manipulate database queries, and execute unauthorized operations on the database.
A proof-of-concept demonstrates a time-based blind SQL injection attack that exploits this vulnerability by causing delays in the database response to confirm the injection.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or deletion of records, and potentially full control over the affected system.
Attackers can disrupt services and compromise the security and integrity of the application and its data.
The exploit is publicly available, increasing the risk of attacks if the vulnerability is not remediated.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /sub-category.php file's pid parameter for SQL injection flaws. One method is to send specially crafted GET requests that include SQL injection payloads to observe if the system behaves abnormally, such as delayed responses.
A proof-of-concept payload to test for a time-based blind SQL injection is: action=wishlist&pid=1' AND (SELECT 9224 FROM (SELECT(SLEEP(5)))kztz) AND 'EawF'='EawF
You can use tools like sqlmap to automate detection. For example, running sqlmap against the vulnerable URL can confirm the presence of the SQL injection.
- Example curl command to test manually: curl "http://target/shopping/sub-category.php?action=wishlist&pid=1' AND (SELECT 9224 FROM (SELECT(SLEEP(5)))kztz) AND 'EawF'='EawF"
- Example sqlmap command: sqlmap -u "http://target/shopping/sub-category.php?action=wishlist&pid=1" --risk=3 --level=5 --batch
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, which prevents SQL injection.
Enforce strict input validation and filtering to ensure that inputs conform to expected formats and block malicious data.
Minimize database user privileges by avoiding the use of high-privilege accounts such as root or admin for routine database operations.
These corrective actions are 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 attackers to gain unauthorized database access, leak sensitive data, modify or delete records, and take control of the system. Such unauthorized access and potential data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity.
Failure to remediate this vulnerability could result in exposure of personal data, violating confidentiality and security requirements mandated by these standards, potentially leading to legal and financial consequences.