dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7266

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was detected in SourceCodester Pizzafy Ecommerce System 1.0. The impacted element is the function save_order of the file /admin/ajax.php?action=save_order. The manipulation of the argument ID results in sql injection. The attack can be executed remotely. The exploit is now public 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 · high confidence

SQL injection vulnerability in SourceCodester Pizzafy Ecommerce System 1.0's save_order function within /admin/ajax.php. The ID parameter passed to the save_order action is not properly sanitized, allowing attackers to inject arbitrary SQL commands. This could enable unauthorized database access, data exfiltration, or potential system compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter in the save_order function. Additionally, implement input validation and apply principle of least privilege to the database account.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Pizzafy Ecommerce System 1.0 installation
    Check for the presence of the application by looking for characteristic files such as index.php, admin/index.php, or configuration files in the web root directory. Check page footers or source code for 'Pizzafy' branding.
    Affected if The application directory structure matches SourceCodester Pizzafy Ecommerce System and no patched version has been confirmed installed.
  2. Confirm vulnerable file exists
    Locate the file /admin/ajax.php in the web application directory. This file should exist in the admin section of the Pizzafy installation.
    Affected if The file /admin/ajax.php exists in the web directory and contains the save_order function.
  3. Identify save_order function in ajax.php
    Open /admin/ajax.php and search for the string 'function save_order' or 'case save_order' to confirm the vulnerable function exists.
    Affected if The save_order function is present in ajax.php and processes the ID parameter without apparent sanitization.
  4. Check admin interface accessibility
    Determine if the /admin/ endpoint is accessible from the network. Check if authentication is required or if the endpoint is exposed.
    Affected if The admin interface at /admin/ajax.php is accessible without additional network restrictions or the application is exposed to untrusted networks.
  5. Verify database user privileges
    Review database configuration files (such as config.php, db.php, or similar) to identify the database user credentials used by the application. Check if the database user has excessive privileges beyond what is required.
    Affected if The application's database user has privileges beyond what is necessary for order management, which could enable data exfiltration or further compromise.

A user is affected if they have SourceCodester Pizzafy Ecommerce System 1.0 installed with the vulnerable /admin/ajax.php file containing an unsanitized ID parameter in the save_order function that is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter in the save_order function. Additionally, implement input validation and apply principle of least privilege to the database account.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7266 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7266 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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