CVE-2026-7267
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the ID parameter of /view_prod.php in SourceCodester Pizzafy Ecommerce System 1.0 allows remote attackers to manipulate SQL queries via unsanitized input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate view_prod.phpSearch the web root for the file view_prod.php (e.g., `find /var/www -name view_prod.php` or list the application's source directory).Affected if The file does not exist in your deployment, meaning the vulnerable endpoint is not present.
-
Identify the product versionLook for a version indicator in files such as README.txt, version.php, or the header comment of any PHP file, or check the admin interface for a version number.Affected if The installed version is 1.0 (the only version listed as affected).
-
Inspect the ID parameter handling in view_prod.phpOpen view_prod.php and search for occurrences of $_GET['id'] or $_POST['id']. Determine whether this variable is inserted directly into an SQL string (e.g., $sql = "SELECT * FROM products WHERE id = " . $_GET['id'];).Affected if The code concatenates the ID parameter into the SQL query without any sanitization or escaping.
-
Verify use of prepared statementsSearch the same file for patterns like 'prepare', 'stmt', 'bindParam', 'bindValue' or 'mysqli_prepare' that handle the ID query. If none are found, the query is not parameterized.Affected if No prepared statement is used for the ID query, indicating the vulnerability is present.
If you are running Pizzafy Ecommerce System version 1.0 and view_prod.php contains direct concatenation of the ID parameter into SQL, you are affected by CVE-2026-7267.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries (prepared statements) for the ID parameter, or implement strict input validation and use least-privilege database accounts.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7267 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data