CVE-2000-0102
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 · uneditedThe SalesCart shopping cart application allows remote users to modify sensitive purchase information via hidden form fields.
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 confidenceThe SalesCart shopping cart application stores sensitive purchase information (prices, quantities, product details) in hidden HTML form fields that are submitted with user requests without server-side validation, allowing attackers to modify these values to purchase items at arbitrary prices or quantities.
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 dataall versionsCVSS 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
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 SalesCart installationSearch web server directories for SalesCart application files, typically found in /shop, /cart, /salescart, or similar paths. Look for files named salescart.asp, shopping.asp, or directories containing 'salescart' in the name.Affected if SalesCart software is present on the server
-
Examine HTML form fields for sensitive dataView the source code of shopping cart pages (checkout, add to cart, order form). Look for <input type="hidden"> tags that contain price, cost, amount, quantity, or total fields.Affected if Hidden form fields contain price, quantity, or total value fields that are submitted to the server
-
Check for server-side validationReview the server-side script that processes the form submission (typically an ASP file). Look for code that validates or retrieves product prices from a database or server-side storage rather than trusting submitted form values.Affected if The order processing script accepts price/quantity values directly from the form without independent validation against server-side data
-
Test for client-side price manipulationSubmit a modified form with altered hidden price or quantity values and observe if the transaction processes at the modified value rather than the original server-defined price.Affected if Modifying hidden form field values (price, quantity, total) changes the final transaction amount
If SalesCart is installed and uses hidden HTML form fields to store price/quantity data without server-side validation, the environment is affected by this vulnerability.
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 dataMove all sensitive purchase data to server-side session storage and validate all transactions against authoritative server-side data before processing orders; never trust client-submitted price or quantity values.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0102 — 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-2000-0102 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