dbcve.org
FileorbisApplication

CVE-2022-3693

HIGH · 7.5 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 10.6.3 or later.
See remediation →
84/100
Remediation priority · High
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
Path Traversal vulnerability in Deytek Informatics FileOrbis File Management System allows Path Traversal. This issue affects FileOrbis File Management System: from unspecified before 10.6.3.

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

A path traversal vulnerability exists in FileOrbis File Management System versions prior to 10.6.3. The vulnerability allows attackers to manipulate file paths using '../' sequences or absolute paths to access files outside the web root directory, potentially exposing sensitive system files or application data.

MitigationUpgrade to FileOrbis File Management System version 10.6.3 or later. Implement strict input validation on all file path parameters, use allowlists for permitted paths, and apply proper access controls on the filesystem.

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
FileorbisApplication
Affected:< 10.6.3

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
High
Integrity
None
Availability
None

CVSS:3.1/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 checks

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

  1. Confirm FileOrbis FMS installation
    Identify whether the FileOrbis File Management System application is present in your environment by checking for its web application components, services, or installed packages.
    Affected if The application is present and serves file management functionality over the network.
  2. Determine installed version
    Locate and read the version information for your FileOrbis installation using the application's admin interface, version file, or package metadata. Compare the version number against the affected range.
    Affected if The installed version is lower than 10.6.3.
  3. Identify exposed file endpoints
    Review your web server configuration and application routing to determine which endpoints accept file path parameters. Look for URLs or API routes that include path variables related to file operations such as download, view, or open.
    Affected if Endpoints accepting user-controlled file path parameters are accessible without authentication or with inadequate access controls.
  4. Test for path traversal capability
    Send a test request to the identified file endpoints using path traversal sequences such as '../' or absolute paths targeting system directories. Observe whether the application returns files from outside the intended web root directory.
    Affected if The application returns files or directories outside the configured document root when traversal sequences are provided.
  5. Inspect access control configuration
    Examine the application's filesystem access controls, allowlist configurations, and input validation rules for file path parameters. Verify whether path traversal sequences are being filtered or sanitized.
    Affected if No input validation or allowlist filtering is applied to file path parameters, or sanitization can be bypassed.

Your environment is affected if FileOrbis File Management System version 10.6.3 or later is not installed AND file path parameters are accessible without proper traversal protections.

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

Upgrade to FileOrbis File Management System version 10.6.3 or later. Implement strict input validation on all file path parameters, use allowlists for permitted paths, and apply proper access controls on the filesystem.

Recommended fix Moderate confidence

FileOrbis 10.6.3

  1. 1. Backup the current FileOrbis installation and database before proceeding with the upgrade.
  2. 2. Download FileOrbis version 10.6.3 or later from the official vendor (Deytek Informatics).
  3. 3. Review the vendor's upgrade documentation for any specific prerequisites or migration steps.
  4. 4. Install the version 10.6.3 update following the standard upgrade procedure.
  5. 5. After installation, verify the path traversal vulnerability is resolved by testing file access controls.
  6. 6. Confirm all other functionalities work as expected in the updated version.

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

Fix this in Fileorbis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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