Skip to main content
VulnerabilityPublished Updated

CVE-2018-10212: Vaultize Enterprise File Sharing

Source CVE Database V5

0

Not known to be exploited.

Data as of 26 Oct 2026, 11:07 UTC

Severity
Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Apr 2018

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =17.05.31
Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should first verify if they are running the affected version (17.05.31) of Vaultize Enterprise File Sharing and prioritize upgrading to a patched or newer version where the authorization flaw is resolved. If an official patch is unavailable, implementing strict network segmentation and access controls to limit exposure of the Vaultize server is critical. Administrators should audit device and session management logs to detect anomalous folder creation activities and enforce multi-factor authentication to reduce the risk of compromised credentials being used to exploit the flaw. Additionally, reviewing and tightening authorization policies within the application configuration can help prevent unauthorized cross-account actions. Employing application-layer firewalls or intrusion detection systems to monitor and block suspicious API calls or parameter tampering attempts related to device values is recommended. Finally, educating users about potential social engineering risks stemming from unauthorized folder creation can reduce the likelihood of follow-on attacks.

Description

An issue was discovered in Vaultize Enterprise File Sharing 17.05.31. There is improper authorization leading to creation of folders within another account via a modified device value.

References

Community reviews

Loading reviews…