CVE-2026-14694
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 vulnerability has been found in SourceCodester Multi-Vendor Online Grocery Management System 1.0. Affected by this issue is the function cancel_order of the file classes/Master.php of the component POST Parameter Handler. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the 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 · moderate confidenceSQL injection vulnerability in the cancel_order function of classes/Master.php in SourceCodester Multi-Vendor Online Grocery Management System 1.0. The POST parameter 'ID' is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL syntax.
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.
-
Confirm SourceCodester Multi-Vendor Online Grocery Management System is installedSearch for the application by checking web server document roots for files typical to this system, or look for the classes/Master.php file referenced in the CVE.Affected if The application is present on the server
-
Locate the vulnerable file classes/Master.phpNavigate to the classes directory in the web application root and verify the presence of Master.php.Affected if The file classes/Master.php exists in the application installation
-
Identify the cancel_order functionOpen classes/Master.php and search for the function definition 'function cancel_order' or 'public function cancel_order'.Affected if The cancel_order function is present in Master.php
-
Check if POST parameter ID is used in SQL queries without sanitizationWithin the cancel_order function, locate code that uses $_POST['ID'] or similar in SQL queries. Look for direct concatenation of the ID parameter into SQL strings without prepared statements, escaping, or validation functions.Affected if The ID POST parameter is used directly in SQL queries without parameterized queries or proper sanitization (such as mysqli_real_escape_string, prepared statements, or input validation)
-
Verify the application processes ordersCheck if the application has order management functionality accessible (look for order-related tables in the database or order-related pages in the web interface).Affected if The application has order processing capabilities and the vulnerable function is reachable via the web interface
The environment is affected if the Multi-Vendor Online Grocery Management System is installed, contains the cancel_order function in classes/Master.php, and the ID POST parameter is used directly in SQL queries without prepared statements or sanitization.
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) in the cancel_order function, and implement proper input validation for the ID parameter. Apply output encoding for any displayed data.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14694 — 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-14694 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