CVE-2026-5560
SQL Injection in PHPGurukul Payment-Method.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 | 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-5560 is a critical SQL injection vulnerability found in version 2.1 of the PHPGurukul Online Shopping Portal Project, specifically in the /payment-method.php file. The issue arises because the "paymethod" parameter is improperly handled and directly included in SQL queries without proper sanitization or validation.
This flaw allows attackers to inject malicious SQL code remotely, manipulating the database queries executed by the application. For example, a time-based blind SQL injection attack can be performed by sending a specially crafted payload that causes a delay in the database response, confirming the vulnerability.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, tampering with data, full system compromise, and potential disruption of services.
- Attackers can manipulate SQL queries to extract confidential information.
- Data integrity can be compromised through unauthorized modifications.
- The entire system could be taken over if attackers exploit the vulnerability fully.
- Service availability might be affected, causing downtime or degraded performance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "paymethod" POST parameter in the /shopping/payment-method.php endpoint for SQL injection flaws.
A proof-of-concept uses a time-based blind SQL injection payload: `paymethod=COD' RLIKE SLEEP(5)-- gsme&submit=submit` which causes a delay in the database response, confirming the injection point.
The sqlmap tool can be used to automate detection by targeting the "paymethod" parameter via POST requests to `/shopping/payment-method.php`.
What immediate steps should I take to mitigate this vulnerability?
Immediate remediation steps include:
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Enforce strict input validation and filtering to ensure inputs conform to expected formats and block malicious data.
- Restrict 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 the PHPGurukul Online Shopping Portal Project 2.1 allows attackers to gain unauthorized database access, leading to potential data leakage and data tampering.
Such unauthorized access and data compromise can result in violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to remediate this vulnerability could lead to non-compliance with these standards due to inadequate protection of data confidentiality, integrity, and availability.