CVE-2026-14691
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 vulnerability has been detected in SourceCodester Multi-Vendor Online Grocery Management System 1.0. This impacts the function update_settings_info of the file classes/SystemSettings.php of the component Setting Handler. Such manipulation of the argument content[] leads to code injection. The attack can be executed remotely. The exploit has been disclosed publicly 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 confidenceCode injection vulnerability in SourceCodester Multi-Vendor Online Grocery Management System 1.0's classes/SystemSettings.php file. The update_settings_info function accepts user input through the content[] parameter without proper sanitization, allowing remote attackers to inject and execute arbitrary code.
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.
-
Identify if Multi-Vendor Online Grocery Management System is installedSearch for the application files, particularly looking for the classes/SystemSettings.php file or any index.php that references 'Multi-Vendor Online Grocery Management System'Affected if The application is present on the system
-
Verify the application versionCheck any version file, README, or meta information in the application root directory for version 1.0Affected if The installed version is 1.0
-
Confirm the vulnerable file existsLocate and verify the presence of classes/SystemSettings.php in the application structureAffected if The file classes/SystemSettings.php exists in the application
-
Check if update_settings_info function is exposedExamine the SystemSettings.php file and determine if the update_settings_info function can be accessed via web request (typically through an admin controller or direct endpoint)Affected if The update_settings_info function is accessible via HTTP request without authentication or with weak access controls
-
Determine if content parameter is processed without sanitizationReview the update_settings_info function code to verify it directly uses the content[] parameter in file operations, eval, include/require, or system commands without input validationAffected if The content[] parameter is processed without proper sanitization or parameterized handling
A user is affected if they have Multi-Vendor Online Grocery Management System version 1.0 installed with the vulnerable SystemSettings.php file where the update_settings_info function processes the content[] parameter without sanitization and is accessible to attackers.
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 strict input validation and sanitization on the content[] parameter in the update_settings_info function. Apply parameterized queries and enforce proper access controls to restrict settings modifications to authorized administrators only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14691 — 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-14691 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