CVE-2026-14693
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 flaw has been found in SourceCodester Multi-Vendor Online Grocery Management System 1.0. Affected by this vulnerability is the function cancel_order of the file classes/Master.php. Executing a manipulation can lead to improper authorization. The attack may be performed from remote. The exploit has been published 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 confidenceSourceCodester Multi-Vendor Online Grocery Management System 1.0 contains an improper authorization vulnerability in the cancel_order function within classes/Master.php. The vulnerability allows remote attackers to manipulate the order cancellation functionality to cancel orders they should not have permission to access or modify, likely through insecure direct object reference (IDOR) via manipulated parameters.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 application and versionLocate the SourceCodester Multi-Vendor Online Grocery Management System installation and determine if version 1.0 is in use. Check for version indicators in source files, README, or application metadata.Affected if The system is SourceCodester Multi-Vendor Online Grocery Management System version 1.0
-
Locate the cancel_order functionInspect the file classes/Master.php and locate the cancel_order function definition. Verify the function exists in the codebase.Affected if The cancel_order function exists in classes/Master.php in version 1.0
-
Review authorization logic in cancel_orderExamine the cancel_order function code for user authentication and authorization checks before order cancellation. Look for session validation, user ID verification, or role checks.Affected if The cancel_order function lacks proper authorization checks validating the requesting user owns or has permission to cancel the specific order
-
Check for IDOR vulnerability in order parametersTest the order cancellation flow by manipulating order_id or related parameters in requests. Compare whether the application validates that the authenticated user owns the order being modified.Affected if Order cancellation can be triggered with manipulated order IDs belonging to other users without proper ownership verification
-
Audit other order modification functionsInspect other order-related functions in classes/Master.php for similar improper authorization patterns. Check if order_id parameters can be manipulated across different functions.Affected if Similar IDOR or improper authorization issues exist in other order modification functions within the same file
A user is affected if the system runs SourceCodester Multi-Vendor Online Grocery Management System 1.0 and the cancel_order function in classes/Master.php allows order cancellation without verifying user ownership of the order.
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 proper authorization checks in the cancel_order function to verify the requesting user owns or has legitimate permission to cancel the specific order being requested. Validate user identity and role-based access controls before allowing any order modification.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14693 — 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-14693 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