CVE-2002-2302
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 · unedited3D3.Com ShopFactory 5.5 through 5.8 allows remote attackers to modify the prices in their shopping carts by modifying the price in a hidden form field.
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 confidenceShopFactory 5.5-5.8 stores product prices in hidden form fields submitted by the client, trusting this client-side data without server-side validation. Attackers can intercept the cart submission and modify the price value before posting, allowing purchase at arbitrary prices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.5= 5.6= 5.8CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Identify ShopFactory installation and versionLocate the ShopFactory installation directory and check version information in the application metadata or configuration files. Compare the installed version to the affected versions (5.5, 5.6, 5.8).Affected if The installed version is 5.5, 5.6, or 5.8.
-
Inspect cart page HTML sourceView the HTML source of a product page with an Add to Cart button. Search for <input type="hidden"> fields containing price-related attributes (such as 'price', 'amount', or numeric values).Affected if Hidden form fields containing price values are present in the generated HTML.
-
Examine order processing codeReview the server-side script that handles cart submission and checkout. Look for code that reads price values directly from POST/GET parameters without cross-referencing an authoritative price list.Affected if The server-side code accepts and processes price values from client-submitted form data without server-side validation against a database.
-
Test price modificationAdd an item to cart, intercept the form submission using a proxy tool, modify the hidden price field to a different value, and submit. Observe if the modified price is accepted and reflected in the order.Affected if The modified price is accepted and the order is processed at the attacker-submitted price.
You are affected if ShopFactory version 5.5, 5.6, or 5.8 is installed AND the application uses hidden form fields to store prices that are not validated server-side before order completion.
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 price validation by storing prices in a server-side database and only passing product IDs to the client; validate submitted prices against the authoritative price list before completing transactions.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2302 — 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-2002-2302 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