CVE-2026-7264
SQL Injection in SourceCodester Pizzafy get_cart_items Function
Publication date: 2026-04-28
Last updated on: 2026-05-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sourcecodester | pizzafy_ecommerce_system | 1.0 |
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-7264 is an Error-Based SQL Injection vulnerability found in the Pizzafy Ecommerce System version 1.0. It occurs in the function get_cart_items within the file /admin/ajax.php when the id parameter is manipulated. The vulnerability arises because the id parameter from the GET request is directly concatenated into an SQL query without proper validation or sanitization.
An attacker can exploit this by injecting malicious SQL commands through the id parameter, causing the database to return error messages that reveal sensitive information such as database names, table structures, usernames, and password hashes.
The vulnerable code uses unsafe concatenation of the id parameter into the SQL query, allowing injection of payloads that manipulate the database query execution.
How can this vulnerability impact me? :
This vulnerability can have several serious impacts:
- Confidentiality: Attackers can gain full exposure of the database schema and user credentials.
- Integrity: Unauthorized deletion or modification of records is possible.
- Availability: The system could be subjected to denial of service through mass deletion of data.
- Privilege Escalation: Attackers may hijack sessions and gain administrative access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable endpoint for SQL injection by manipulating the 'id' parameter in the GET request to the endpoint `/pizzafy/admin/ajax.php?action=get_cart_items&id=6`.
A common detection technique is to inject SQL payloads that cause the database to return error messages containing sensitive information, such as using the `updatexml()` function.
Example command to test the vulnerability via HTTP request:
- GET /pizzafy/admin/ajax.php?action=get_cart_items&id=6 AND updatexml(1,concat(0x7e,database()),1)#
Monitoring and logging unusual database activity and error messages can also help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Remove direct assignment of user input from `$_GET['id']` to variables used in SQL queries.
- Use prepared statements with parameterized queries to safely bind user inputs, preventing SQL injection.
- Cast user identifiers to integers or validate and sanitize all input parameters, especially the 'id' parameter.
- Restrict database user privileges to minimize potential damage from injection attacks.
- Avoid exposing detailed database error messages to end users to prevent leakage of sensitive information.
- Implement monitoring and logging to detect unusual database activity.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Pizzafy Ecommerce System 1.0 allows attackers to access sensitive data such as database schema, user credentials, and potentially personal information. This exposure can lead to unauthorized disclosure of personal data, which may violate data protection regulations like GDPR and HIPAA that require safeguarding personal and sensitive information.
Additionally, the vulnerability enables unauthorized modification or deletion of records, which compromises data integrity and availability. Such impacts can hinder compliance with standards that mandate data accuracy, integrity, and availability.
Failure to remediate this vulnerability and prevent unauthorized access or data breaches could result in non-compliance with these regulations, potentially leading to legal penalties, reputational damage, and loss of customer trust.