CVE-2026-7267
Received Received - Intake
SQL Injection in SourceCodester Pizzafy /view_prod.php Allows Remote Exploit

Publication date: 2026-04-28

Last updated on: 2026-04-29

Assigner: VulDB

Description
A flaw has been found in SourceCodester Pizzafy Ecommerce System 1.0. This affects an unknown function of the file /view_prod.php. This manipulation of the argument ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been published and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-28
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2026-04-28
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester pizzafy_ecommerce_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-7267 is an Error-Based SQL Injection vulnerability found in the Pizzafy Ecommerce System version 1.0, specifically in the /pizzafy/view_prod.php file via the id parameter.

The vulnerability occurs because the id parameter is not properly sanitized before being used directly in an SQL query, allowing attackers to inject malicious SQL commands.

Attackers exploit this by using error-based SQL injection techniques, such as the extractvalue() function, to force the database to reveal sensitive information through error messages.


How can this vulnerability impact me? :

This vulnerability can have multiple impacts including:

  • Confidentiality: Exposure of the full database schema, usernames, and password hashes.
  • Integrity: Unauthorized deletion or modification of database records.
  • Availability: Potential mass deletion of data causing denial of service.
  • Privilege Escalation: Attackers may hijack sessions and gain administrative access by extracting session data.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This SQL injection vulnerability can be detected by sending specially crafted HTTP GET requests to the vulnerable endpoint and observing the responses for error messages or unexpected data.

A proof-of-concept command to test the vulnerability is to use curl or a similar tool to send a request that injects an error-based SQL payload into the id parameter, for example:

  • curl "http://<target>/pizzafy/view_prod.php?id=9 AND extractvalue(1, concat(0x7e, (SELECT table_name FROM information_schema.tables WHERE table_schema=database() LIMIT 0,1))) -- "

If the response contains database error messages revealing schema information, it indicates the presence of the vulnerability.

Additionally, monitoring logs for unusual database query patterns or error messages can help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include sanitizing and validating the input parameter 'id' to ensure it only accepts valid integers.

Use prepared statements with parameterized queries to prevent SQL injection by safely binding user input.

  • Validate 'id' using filter_input with FILTER_VALIDATE_INT.
  • Replace direct query execution with prepared statements, for example:
  • $id = filter_input(INPUT_GET, 'id', FILTER_VALIDATE_INT);
  • $stmt = $conn->prepare("SELECT * FROM product_list WHERE id = ?");
  • $stmt->bind_param("i", $id);
  • $stmt->execute();
  • $result = $stmt->get_result();

Also, implement error handling that does not expose database error details to users, restrict database user privileges to limit potential damage, and monitor logs for suspicious activity.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This SQL Injection vulnerability in the Pizzafy Ecommerce System allows attackers to extract sensitive information such as database schema, usernames, and password hashes, which can lead to unauthorized access and data breaches.

Such exposure of sensitive data can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information against unauthorized access and breaches.

Additionally, the vulnerability can lead to integrity and availability issues, such as unauthorized data modification or deletion and denial of service, further impacting compliance with standards that require data integrity and availability.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart