CVE-2016-1208
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 server in Apple FileMaker before 14.0.4 on OS X allows remote attackers to read PHP source code via unspecified vectors.
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 Server web component contains a vulnerability allowing remote unauthenticated attackers to read arbitrary PHP source code from the server file system. This information disclosure could expose credentials, application logic, and database connection details.
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 versions<= 14.0.3CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Verify FileMaker Server is installedCheck for FileMaker Server installation by looking for /Library/FileMaker Server/ directory on Mac OS X, or check Programs and Features (Windows) for FileMaker Server entryAffected if FileMaker Server is present on the system
-
Determine installed FileMaker Server versionOn Mac OS X, open /Library/FileMaker Server/admin/admin-helper/Contents/Info.plist and look for CFBundleVersion, or access the Admin Console and check the Server version under General SettingsAffected if Version is 14.0.3 or earlier (14.0.0 through 14.0.3)
-
Confirm web publishing component is enabledCheck the FileMaker Server Admin Console under Web Publishing > PHP. Verify that PHP is enabled and the web publishing engine is runningAffected if PHP and web publishing are enabled (vulnerability requires PHP to be active)
-
Check network exposure of web publishing portReview firewall rules or network configuration to determine if port 80/443 (HTTP/HTTPS) used by FileMaker Web Publishing is exposed to untrusted networks or the internetAffected if Port 80/443 is accessible from untrusted network sources (remote attackers require network access)
You are affected if FileMaker Server version 14.0.3 or earlier is installed with PHP web publishing enabled and exposed to network access.
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 dataUpgrade FileMaker Server to version 14.0.4 or later. If immediate patching is not feasible, restrict network access to the FileMaker web publishing port and disable any unnecessary PHP file handlers.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1208 — 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-2016-1208 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