dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Mar 2026.
FilezenApplication · Soliton

CVE-2026-25108

HIGH · 8.8 CVSS v3.1 Published 2026-02-13
Fix available
A fix is available. Upgrade to 5.0.11 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable 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
FileZen contains an OS command injection vulnerability. When FileZen Antivirus Check Option is enabled, a logged-in user may send a specially crafted HTTP request to execute an arbitrary OS command.

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 confidence

FileZen versions prior to the patch contain an OS command injection vulnerability in the Antivirus Check functionality. An authenticated user can send a specially crafted HTTP request that, when the antivirus check option is enabled, allows execution of arbitrary OS commands due to improper input validation in the command execution path.

MitigationDisable the FileZen Antivirus Check Option until vendor patch is available; if required, apply strict input validation/sanitization to the antivirus check parameter and implement allowlist-based command construction to prevent injection.

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
FilezenApplication
Affected:>= 4.2.1, < 5.0.11

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check the installed FileZen version
    Access the FileZen administration interface or check the software inventory. Typically, version information is visible in the product's 'About' or 'System Information' page within the admin panel.
    Affected if The installed version is 4.2.1 or higher but lower than 5.0.11.
  2. Verify whether the Antivirus Check Option is enabled
    In the FileZen admin panel, navigate to the antivirus or scanning configuration settings. Look for an option labeled 'Antivirus Check', 'Antivirus Scanning', or similar. Confirm whether this feature is toggled to 'Enabled' or 'On'.
    Affected if The Antivirus Check Option is currently enabled.
  3. Review user account access and privilege levels
    Examine the user management section of the FileZen admin interface. Identify which authenticated users have access to file transfer or upload functionality that triggers the antivirus scanning feature.
    Affected if There are authenticated users with access to file upload or transfer features who could trigger the antivirus scan function.
  4. Inspect server logs for unusual command execution patterns
    Review FileZen server logs and system audit logs for entries containing suspicious shell metacharacters (such as ;, |, &, $(), or backticks) in file paths or parameters associated with antivirus scan operations.
    Affected if Log entries show unexpected command syntax or shell invocations in antivirus-related operations.

A system is affected if FileZen version is between 4.2.1 and 5.0.11 inclusive AND the Antivirus Check Option is currently enabled, allowing an authenticated user to potentially inject OS commands through the antivirus scanning feature.

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 5.0.11 or later
Fixed in 5.0.11
Interim mitigation

Disable the FileZen Antivirus Check Option until vendor patch is available; if required, apply strict input validation/sanitization to the antivirus check parameter and implement allowlist-based command construction to prevent injection.

Recommended fix High confidence

FileZen version 5.0.11 or later

  1. 1. Identify the current FileZen version by checking the system administration interface or running: filezen -v or checking /opt/filezen/version
  2. 2. Confirm that the FileZen Antivirus Check Option is enabled in the configuration (this is a prerequisite for exploitation)
  3. 3. Obtain FileZen version 5.0.11 or later from the official vendor at www.soliton.co.jp
  4. 4. Back up all FileZen configuration files and data before upgrading
  5. 5. Stop the FileZen service: systemctl stop filezen or service filezen stop
  6. 6. Install the upgraded package using the vendor's recommended installation method
  7. 7. Start the FileZen service: systemctl start filezen or service filezen start
  8. 8. Verify the upgrade was successful by checking the version number
Caveat Review vendor release notes for version 5.0.11 to check for any configuration or behavioral changes that may affect existing workflows

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

Fix this in Filezen Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25108 — 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-2026-25108 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