CVE-2026-5641
SQL Injection in PHPGurukul update-image1.php Enables 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 | to 2.1 (inc) |
| phpgurukul | online_shopping_portal | 2.1 |
| 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-5641 is a critical SQL injection vulnerability found in the PHPGurukul Online Shopping Portal Project version 2.1. It exists in the /admin/update-image1.php file, specifically in the handling of the "filename" parameter. The vulnerability arises because the filename parameter is improperly sanitized and directly incorporated into SQL queries, allowing attackers to inject malicious SQL code.
An attacker can exploit this vulnerability remotely by sending specially crafted requests that manipulate the filename argument, enabling unauthorized database access and manipulation.
How can this vulnerability impact me? :
Exploitation of this SQL injection vulnerability can lead to unauthorized access to the database, leakage of sensitive data, manipulation or deletion of data, full system control by the attacker, and potential disruption of services.
- Unauthorized database access
- Data leakage
- Data manipulation or deletion
- Full system compromise
- Service disruption
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/update-image1.php endpoint for SQL injection in the filename parameter. A proof-of-concept involves sending a specially crafted multipart/form-data POST request with a malicious filename parameter that includes a time-based SQL injection payload, such as using a delay function like RLIKE SLEEP(5).
The vulnerability was identified and tested using the sqlmap tool, which can automate detection of SQL injection flaws.
- Use sqlmap to test the target URL with the vulnerable parameter, for example: sqlmap -u "http://target/admin/update-image1.php" --data="productimage1=filename" --technique=BEUSTQ
- Manually craft a POST request with multipart/form-data including the filename parameter with a payload like: filename" RLIKE SLEEP(5) #
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, preventing SQL injection.
- Implement strict input validation and filtering to ensure that inputs conform to expected formats.
- Minimize database user permissions by avoiding elevated privilege accounts for routine operations.
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 unauthorized access and potential exposure of sensitive data can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information.
Failure to mitigate this vulnerability could result in breaches of confidentiality, integrity, and availability of data, which are core principles in these regulations. This may lead to legal penalties, loss of customer trust, and other compliance-related consequences.