dbcve.org
Filecatalyst DirectApplication · Fortra

CVE-2024-25154

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 3.8.9 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Improper URL validation leads to path traversal in FileCatalyst Direct 3.8.8 and earlier allowing an encoded payload to cause the web server to return files located outside of the web root which may lead to data leakage.  

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 confidence

Path traversal vulnerability in FileCatalyst Direct's web server allows attackers to use encoded URL payloads to access files outside the web root directory due to improper URL validation. This enables unauthorized access to sensitive files potentially located anywhere on the host filesystem.

MitigationApply vendor patch for FileCatalyst Direct 3.8.8 or later; implement proper URL path validation and sanitization to reject traversal sequences.

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
Filecatalyst DirectApplication
Affected:>= 3.0.0, < 3.8.9

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FileCatalyst Direct installation
    Check for FileCatalyst Direct installation by looking for the product directory, service, or executable. Common locations include C:\Program Files\FileCatalyst or /opt/FileCatalyst on Linux. Also check for running processes named 'FileCatalyst' or 'fcserver'.
    Affected if FileCatalyst Direct is installed on the system
  2. Determine installed version
    Locate the version information in the installation directory. Typically found in a version.txt, about dialog, or in the fcserver.exe/fcserver binary metadata. Check the manifest or properties file for the exact version number.
    Affected if Installed version is 3.0.0 or higher but lower than 3.8.9
  3. Verify web server component is enabled
    Check if the FileCatalyst Direct web server component is running and exposed. Look for configuration files (server.xml, config.xml) in the installation directory and check for HTTP/HTTPS listener ports (commonly 8080, 8443, or configured ports). Verify the fcserver service or process is active.
    Affected if The FileCatalyst Direct web server is running and accessible over the network
  4. Inspect URL validation configuration
    Examine the web server configuration files for URL validation settings. Look for any existing restrictions on path traversal sequences. Check server.xml or similar config files for path validation or whitelist settings.
    Affected if URL validation is absent, weak, or allows encoded traversal sequences (%2e%2e%2f or similar)
  5. Test for path traversal vulnerability
    If authorized and safe to do so, send a crafted request with encoded path traversal sequences (such as %2e%2e%2f or ..%2f) to the web server endpoint and observe if the response returns files outside the intended web root directory.
    Affected if The web server returns files or directories outside the configured web root

The environment is affected if FileCatalyst Direct version 3.0.0 through 3.8.8 is installed with the web server component enabled and accessible, and the URL validation does not properly reject encoded path traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.8.9 or later
Fixed in 3.8.9
Interim mitigation

Apply vendor patch for FileCatalyst Direct 3.8.8 or later; implement proper URL path validation and sanitization to reject traversal sequences.

Recommended fix High confidence

3.8.9 or later

  1. Backup the current FileCatalyst Direct installation, configuration files, and any existing data
  2. Stop the FileCatalyst Direct service
  3. Download FileCatalyst Direct version 3.8.9 or later from the official Fortra/FileCatalyst download portal
  4. Install the updated version following the standard installation procedures
  5. Verify the installation was successful and the service starts without errors
  6. Confirm the path traversal vulnerability is resolved by testing URL validation with encoded traversal sequences
  7. Restart the FileCatalyst Direct service

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Filecatalyst Direct Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25154 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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