dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14692

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-05
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 6 weeks old

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 Multi-Vendor Online Grocery Management System 1.0/5.7.26. Affected is the function save_shop_type of the file classes/Master.php of the component POST Parameter Handler. Performing a manipulation results in sql injection. The attack is possible to be carried out 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 the save_shop_type function of classes/Master.php in SourceCodester Multi-Vendor Online Grocery Management System 1.0/5.7.26. The POST parameter handler fails to properly sanitize input, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement prepared statements/parameterized queries for all database operations in the affected function and similar code paths. Apply input validation and enforce least-privilege database accounts.

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. Identify if Multi-Vendor Online Grocery Management System is installed
    Locate the application by searching for typical SourceCodester PHP application structures - check web root directories for folders containing 'grocery', 'vendor', or similar naming. Look for an index.php entry point.
    Affected if The application SourceCodester Multi-Vendor Online Grocery Management System is found on the system
  2. Verify the application version
    Examine version information in the application - check for a version file, readme, or any file containing '1.0' or '5.7.26'. Look in the root directory for version indicators.
    Affected if The installed version matches 1.0 or shows 5.7.26 in version strings
  3. Locate the vulnerable Master.php file
    Search for the file classes/Master.php within the application directory structure. This file should exist in a 'classes' subfolder.
    Affected if The file classes/Master.php exists in the application
  4. Examine the save_shop_type function for SQL injection vulnerability
    Open classes/Master.php and locate the save_shop_type function. Inspect the function for direct use of POST parameters in SQL queries without prepared statements, parameterized queries, or input sanitization functions.
    Affected if The save_shop_type function contains SQL queries that directly incorporate POST parameters without sanitization or parameterization
  5. Check if the vulnerable code path is reachable
    Determine if the application has an active web interface that can receive POST requests to trigger the save_shop_type function. Look for form submissions or API endpoints that call this function.
    Affected if The application is running and accessible via web, allowing POST requests to reach the vulnerable function

The system is affected if the Multi-Vendor Online Grocery Management System version 1.0 is installed with the classes/Master.php file containing the save_shop_type function that processes unsanitized POST parameters in SQL queries.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations in the affected function and similar code paths. Apply input validation and enforce least-privilege database accounts.

Recommended fix Moderate confidence
  1. 1. Locate the file classes/Master.php in the application directory
  2. 2. Find the save_shop_type function within the Master.php file
  3. 3. Identify the POST parameter(s) used in the SQL query within this function
  4. 4. Replace string concatenation or direct interpolation of POST parameters in SQL queries with prepared statements/parameterized queries
  5. 5. For example, if the current code uses: $sql = "INSERT INTO shop_types (name) VALUES ('" . $_POST['name'] . "')", change it to use: $stmt = $pdo->prepare("INSERT INTO shop_types (name) VALUES (:name)"); $stmt->execute(['name' => $_POST['name']])
  6. 6. Apply the same parameterized query pattern to all SQL queries in the function that accept user input
  7. 7. Test the save_shop_type functionality to verify the fix works correctly
  8. 8. Deploy the updated Master.php file to production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14692 — 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-14692 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