CVE-2026-14713
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 security flaw has been discovered in SourceCodester Pizzafy E-Commerce System 1.0. This vulnerability affects unknown code of the file /admin/ajax.php?action=confirm_order. The manipulation of the argument ID results in sql injection. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks.
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 confidenceSQL injection vulnerability in SourceCodester Pizzafy E-Commerce System 1.0 allows remote attackers to manipulate the ID parameter in the /admin/ajax.php?action=confirm_order endpoint, potentially enabling unauthorized database access, data exfiltration, or administrative account compromise.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Pizzafy E-Commerce System installationSearch the web root directory for files or directories containing 'pizzafy' or check application startup files for product name brandingAffected if The application is SourceCodester Pizzafy E-Commerce System
-
Verify the version is 1.0Check the application version from any version file, about page, or changelog typically found in the web root or admin areaAffected if The installed version is 1.0 (or if version cannot be determined but the product matches)
-
Locate the vulnerable ajax.php fileNavigate to the /admin/ directory in the web root and confirm ajax.php existsAffected if The file admin/ajax.php exists in the web application directory
-
Inspect the confirm_order handler in ajax.phpOpen admin/ajax.php and locate the code block handling the 'confirm_order' action; examine how the ID parameter from $_GET or $_POST is used in database queriesAffected if The ID parameter is directly interpolated into SQL queries without prepared statements or parameter binding
-
Verify the ID parameter is not sanitizedReview the code around the confirm_order action to see if the ID parameter undergoes any escaping, type casting, or validation before being used in SQLAffected if The ID parameter is used in SQL queries without proper escaping, type validation, or prepared statement usage
If Pizzafy E-Commerce System version 1.0 is installed with the admin/ajax.php file containing a confirm_order action that uses the ID parameter directly in SQL queries without parameterized binding, the environment is affected.
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 dataImplement prepared statements/parameterized queries for all database interactions, particularly in the confirm_order action, and add input validation for the ID parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14713 — 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-14713 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