CVE-2023-45854
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 Business Logic vulnerability in Shopkit 1.0 allows an attacker to add products with negative quantities to the shopping cart via the qtd parameter in the add-to-cart function.
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 confidenceShopkit 1.0 fails to validate the qtd (quantity) parameter in the add-to-cart function, allowing attackers to submit negative values. This business logic flaw permits negative quantities to be added to the shopping cart, potentially enabling inventory manipulation, negative pricing exploits, or other logical abuse of the e-commerce workflow.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 Shopkit installation and versionLocate Shopkit installation files (e.g., check for shopkit/ directory, composer.json, or version.php). Look for version identifiers in typical locations like includes/version.php, or in the application metadata.Affected if The installed version is Shopkit 1.0 or earlier without the fix applied.
-
Locate the add-to-cart functionalitySearch the codebase for the add-to-cart handler. Look for files handling cart operations, typically named cart.php, add_to_cart.php, or within a /cart/ controller directory. Identify the code that processes the 'qtd' or 'quantity' parameter.Affected if The add-to-cart function exists and processes a quantity parameter named 'qtd' or 'quantity' without sufficient validation.
-
Inspect quantity parameter validation logicExamine the add-to-cart code found in the previous step. Look for server-side validation that checks the quantity value BEFORE processing. Search for conditional statements, type checks, or range validation applied to the qtd/quantity input.Affected if No validation exists, or validation can be bypassed, allowing negative, zero, or non-integer values to pass through.
-
Check for business logic enforcement on quantityReview whether the application enforces minimum quantity limits (e.g., minimum of 1) at the application layer. Look for code that rejects values less than 1 or performs integer type checking on the quantity parameter.Affected if The application accepts any numeric value for quantity without enforcing positive integer constraints.
A user is affected if Shopkit 1.0 is running with the add-to-cart function accepting negative or zero values for the quantity parameter without proper server-side validation.
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 server-side input validation to reject negative, zero, or non-integer values for the quantity parameter, and enforce minimum quantity limits at the application layer.
- 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-2023-45854 — 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-2023-45854 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