CVE-2025-46294
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 · uneditedTo enhance security, the FileMaker Server 22.0.4 installer now includes an option to disable IIS short filename enumeration by setting NtfsDisable8dot3NameCreation in the Windows registry. This prevents attackers from using the tilde character to discover hidden files and directories. This vulnerability has been fully addressed in FileMaker Server 22.0.4. The IIS Shortname Vulnerability exploits how Microsoft IIS handles legacy 8.3 short filenames, allowing attackers to infer the existence of files or directories by crafting requests with the tilde (~) character.
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 confidenceThis is an information disclosure vulnerability in FileMaker Server on Windows where IIS short filename enumeration allows attackers to discover hidden files and directories by using the tilde (~) character in HTTP requests. The 8.3 naming convention legacy feature in Windows creates shortened versions of filenames that can be enumerated.
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< 22.0.4CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm FileMaker Server is installedCheck for FileMaker Server installation directory, typically at C:\Program Files\FileMaker\ or look for FileMaker Server services in Windows Services (fmserver, fmsadmin).Affected if FileMaker Server is installed on this Windows host.
-
Identify installed FileMaker Server versionCheck the FileMaker Server version: Open FileMaker Server Admin Console or check the version in the installation directory, or run 'fmsadmin -v' from the command line if available.Affected if Version is lower than 22.0.4.
-
Verify IIS short filename enumeration is possibleAttempt to access a known file on the FileMaker Server web root using IIS short filename format (e.g., request a URL with ~1 or ~2 suffix). Alternatively, check if the NtfsDisable8dot3NameCreation registry key exists under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem and note its value (1 means disabled, 0 or missing means enabled).Affected if NtfsDisable8dot3NameCreation is set to 0 or the registry key is missing, allowing 8.3 short filename creation.
-
Confirm IIS is serving FileMaker Web Direct or Web PublishingVerify that IIS is configured with FileMaker Web Publishing or Web Direct modules enabled, as this exposes the web server interface where short filename enumeration can be performed.Affected if IIS is running with FileMaker web publishing components enabled.
The environment is affected if FileMaker Server version is below 22.0.4 AND NtfsDisable8dot3NameCreation is not set to 1 (disabled), allowing IIS short filename enumeration to discover hidden files.
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.
dbcve · scoped22.0.4
Upgrade to FileMaker Server 22.0.4 or later, which includes an option to disable IIS short filename enumeration by setting NtfsDisable8dot3NameCreation in the Windows registry.
FileMaker Server 22.0.4
- Download FileMaker Server 22.0.4 from the official Claris/Filemaker support site (support.claris.com)
- Run the FileMaker Server 22.0.4 installer on the Windows server
- During the installation process, select the option to disable IIS short filename enumeration (NtfsDisable8dot3NameCreation)
- Complete the installation following the on-screen prompts
- Verify the NtfsDisable8dot3NameCreation registry setting is configured to disable 8.3 name creation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46294 — 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-2025-46294 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