dbcve.org
FilecloudApplication

CVE-2022-1958

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 21.3.5.18513 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A vulnerability classified as critical has been found in FileCloud. Affected is an unknown function of the component NTFS Handler. The manipulation leads to improper access controls. It is possible to launch the attack remotely. Upgrading to version 21.3.5.18513 is able to address this issue. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-201960.

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

FileCloud versions prior to 21.3.5.18513 contain an improper access control vulnerability in the NTFS Handler component, allowing remote attackers to potentially access files or resources they shouldn't have permission to access.

MitigationUpgrade FileCloud to version 21.3.5.18513 or later to remediate this vulnerability.

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
FilecloudApplication
Affected:>= 21.2, < 21.3.5.18513

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify FileCloud installation
    Locate the FileCloud installation directory, typically under /var/www/html/filecloud or C:\xampp\htdocs\filecloud on Windows servers. Check for the presence of core files like index.php or the FileCloud administrative interface.
    Affected if FileCloud is not installed - not applicable to this CVE
  2. Determine installed FileCloud version
    Access the FileCloud admin panel and navigate to Settings > About, or inspect the file /var/www/html/filecloud/sources/server/version.php (or the equivalent version file in your installation). Look for the version number displayed.
    Affected if Version is 21.2 or higher but lower than 21.3.5.18513 - user is potentially affected
  3. Verify NTFS Handler is in use
    Check FileCloud configuration files (typically in /var/www/html/filecloud/sources/config.php or similar config location) for NTFS storage handler settings. The vulnerability exists in the NTFS Handler component specifically.
    Affected if NTFS storage handler is enabled and configured, combined with a vulnerable version - user is affected
  4. Check for exposed FileCloud web interface
    Verify the FileCloud web interface is accessible from network. Test with: curl -I https://your-filecloud-server/ or http://your-filecloud-server/ to confirm it responds.
    Affected if Web interface is publicly or broadly accessible with a vulnerable version - exploitation is possible

User is affected if FileCloud version is 21.2 or higher but below 21.3.5.18513 AND the NTFS Handler component is enabled in their configuration.

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

Upgrade FileCloud to version 21.3.5.18513 or later to remediate this vulnerability.

Recommended fix High confidence

21.3.5.18513

  1. Verify current FileCloud version by accessing the admin dashboard or checking the installation
  2. Download the fixed version 21.3.5.18513 from the official FileCloud download portal
  3. Review FileCloud upgrade documentation for your deployment type (Windows or Linux)
  4. Create a complete backup of the FileCloud database and file storage before upgrading
  5. Stop the FileCloud services
  6. Install version 21.3.5.18513 using the standard upgrade procedure
  7. Restart FileCloud services
  8. Verify the upgrade was successful by checking the admin dashboard version and testing NTFS handler functionality

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

Fix this in Filecloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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