CVE-2002-2303
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.8 uses client-side encryption and decryption for sensitive price data, which allows remote attackers to modify shopping cart prices by using the Javascript to decrypt the cookie that contains the data.
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.8 stores sensitive price data in cookies using JavaScript-based client-side encryption. Attackers can reverse this encryption by examining the JavaScript code and decrypt/modify the cookie values to alter shopping cart prices before checkout.
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.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
- None
- Integrity
- Complete
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:C/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 versionCheck for ShopFactory installation directories or examine web application files for ShopFactory version markers. Common locations include the root web directory. Look for version files, about pages, or headers mentioning 'ShopFactory' and version '5.8'.Affected if ShopFactory version 5.8 is installed and running
-
Locate JavaScript files handling price encryptionSearch the web application directory for JavaScript files (.js) that contain encryption, encoding, or cipher functions related to shopping cart or price handling. Examine files in scripts, js, or similar directories. Look for functions that encrypt/decrypt price data.Affected if JavaScript files contain custom encryption functions for price data in cookies
-
Inspect cookies for price-related dataBrowse the shop website, add items to cart, and use browser developer tools or command-line tools (curl) to examine cookies set by the domain. Look for cookies containing encoded or encrypted numeric values that correspond to product prices.Affected if Cookies contain price values in encrypted or encoded form accessible to client-side JavaScript
-
Verify client-side price calculation existsExamine JavaScript code for functions that read cookie values, decrypt them, and use them in price calculations or checkout processes. Check for code that performs mathematical operations on cookie-derived values to determine totals.Affected if JavaScript code reads cookie price values and uses them in checkout calculations without server-side validation
A user is affected if ShopFactory 5.8 is installed and the application uses JavaScript-based cookie encryption to store or process shopping cart prices.
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 dataMigrate all price calculation and storage to server-side processing with validated database values; remove client-side price handling entirely and implement server-side integrity verification.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2303 — 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-2303 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