CVE-2026-7293
SQL Injection in SourceCodester Pizzafy delete_category Function
Publication date: 2026-04-28
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 |
|---|---|---|
| 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-7293 is an Error-Based SQL Injection vulnerability found in the Pizzafy Ecommerce System version 1.0, specifically in the delete_category function accessed via the endpoint /pizzafy/admin/ajax.php?action=delete_category.
The vulnerability occurs because the id parameter used in the SQL DELETE query is not properly sanitized, allowing attackers to inject malicious SQL commands.
This means an attacker can manipulate the id argument to execute arbitrary SQL code on the database, potentially causing the database to reveal sensitive information through error messages.
For example, an attacker can use a payload that forces the database to return the current database name via an error message.
How can this vulnerability impact me? :
This vulnerability can have several serious impacts:
- Confidentiality: Exposure of the full database schema and user credentials.
- Integrity: Unauthorized deletion or modification of database records.
- Availability: Potential 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 `/pizzafy/admin/ajax.php?action=delete_category` for SQL injection in the `id` parameter. An example method is to send crafted POST requests with SQL injection payloads and observe error messages or unexpected behavior.
- Use a command-line tool like curl to send a POST request with a malicious payload, for example: curl -X POST -d "id=-11 OR extractvalue(1,concat(0x7e,database())) -- " http://target/pizzafy/admin/ajax.php?action=delete_category
- Monitor database error messages returned by the application, which may reveal sensitive information due to the error-based SQL injection.
- Use automated vulnerability scanners or penetration testing tools that support SQL injection detection against the specified endpoint.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating the `id` parameter by casting it to an integer and ensuring it is positive before use.
Use prepared statements with parameterized queries to prevent SQL injection attacks.
Restrict database user privileges to minimize potential damage from exploitation.
Implement proper error handling to avoid exposing database error messages to users.
Conduct regular security testing, including penetration tests and code reviews, and monitor unusual database access patterns.
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 can lead to unauthorized exposure of sensitive data, including full database schema and user credentials, which directly impacts confidentiality.
Such exposure and potential unauthorized modification or deletion of data can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
The vulnerability also risks availability and integrity of data, further complicating compliance with standards that require data accuracy and availability.