CVE-2000-0123
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 shopping cart application provided with Filemaker 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 FileMaker shopping cart application stores sensitive purchase information (such as prices, product IDs, or quantities) in hidden form fields that are submitted with each request. Attackers can intercept these HTTP requests and modify the hidden field values before submission, allowing them to change prices, quantities, or other transaction parameters to their advantage.
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 FileMaker web applicationInspect your web server for FileMaker web publishing (Web Companion, XML publishing, or PHP/Perl APIs) or check if the application is accessible via HTTP/HTTPS and appears to be FileMaker-based.Affected if The environment runs a FileMaker-based web application accessible over HTTP/HTTPS.
-
Inspect HTML forms for hidden fieldsView the page source (right-click > View Page Source) of shopping cart pages and search for <input type="hidden"> tags. Look for field names that suggest sensitive data such as price, cost, quantity, productid, or itemid.Affected if Hidden input fields containing transaction-related parameters like price, quantity, or product identifiers are present in the HTML.
-
Verify client-side dependency of transaction dataSubmit a test purchase request using a web proxy (like Burp Suite or OWASP ZAP) or by modifying the HTML form and resubmitting it. Change the values in hidden fields (e.g., modify a price value from 100 to 1) and observe if the server accepts the altered value without revalidation.Affected if The server accepts and processes transaction parameter values from hidden form fields without performing independent validation.
-
Check for server-side validation mechanismsReview server-side scripts (PHP, Perl, or FileMaker scripts) that process the form submissions. Verify whether the application independently retrieves pricing/inventory data from the database rather than trusting submitted form values.Affected if No server-side validation exists for price, quantity, or product data, or the application does not cross-reference submitted values against authoritative server-side data.
If your FileMaker shopping cart application uses hidden HTML form fields to store prices, quantities, or product IDs and the server accepts these values without independent validation, your 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 dataImplement server-side validation: never trust client-side data for sensitive transaction parameters. Store all pricing and transaction data server-side and only reference records by non-editable identifiers.
- 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-2000-0123 — 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-0123 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