CVE-2000-0386
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 · uneditedFileMaker Pro 5 Web Companion allows remote attackers to send anonymous or forged email.
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 confidenceFileMaker Pro 5 Web Companion contains a vulnerability that allows unauthenticated remote attackers to relay or spoof email through the affected server. The web publishing component fails to properly authenticate or validate SMTP requests, enabling anonymous email transmission.
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.0CVSS 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.
-
Verify FileMaker Pro versionCheck the installed FileMaker Pro version on the system. This can typically be done by opening FileMaker Pro and selecting About from the Help menu, or checking Add/Remove Programs for FileMaker Pro 5.0.Affected if FileMaker Pro version 5.0 is installed
-
Confirm Web Companion is enabledCheck if the Web Companion component is installed and enabled. In FileMaker Pro 5, this is a separate component that enables web publishing. Check for the presence of Web Companion files or look in the FileMaker Server/Pro configuration for Web Companion settings.Affected if Web Companion feature is installed and active on the system
-
Inspect SMTP server configurationCheck the SMTP configuration for FileMaker Pro or the underlying web server. Look for SMTP relay settings or mail server configuration that may allow unauthenticated email transmission.Affected if SMTP is configured without requiring authentication or allowing open relay
-
Check network exposure of Web CompanionDetermine if the Web Companion web publishing port (typically port 80 or 443) is exposed to external networks or untrusted users.Affected if Web Companion is accessible from external or untrusted networks without firewall protection
A system is affected if FileMaker Pro 5.0 is installed with Web Companion enabled and the SMTP configuration does not require authentication, exposing the server to unauthenticated email relay.
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 dataIsolate the FileMaker Pro 5 server from external networks or disable the Web Companion feature if unused. For continued use, upgrade to a supported FileMaker version with current security patches and implement SMTP authentication.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0386 — 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-0386 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