Skip to main content
VulnerabilityPublished Updated

CVE-2018-10211: Vaultize Enterprise File Sharing

Source CVE Database V5

0

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity
High

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

EPSS
1.0% chance of exploitation in 30 days – higher than 63% 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 CVE-2018-10211, European organizations using Vaultize Enterprise File Sharing should: 1) Immediately review and restrict access to session management mechanisms, ensuring that session IDs are securely generated, stored, and validated server-side without relying solely on client-side data. 2) Implement strict server-side authorization checks that verify the user’s identity against requested resources, preventing unauthorized access through manipulated cookies. 3) Employ secure cookie attributes such as HttpOnly, Secure, and SameSite to reduce the risk of session hijacking or fixation. 4) Monitor and audit access logs for unusual session activity or attempts to access other users’ histories. 5) Engage with the vendor or community to obtain patches or updates addressing this vulnerability; if unavailable, consider alternative secure file sharing solutions. 6) Educate users on secure session practices and encourage the use of multi-factor authentication to reduce the risk of session compromise. 7) Conduct penetration testing focused on session management and access control to identify and remediate similar issues proactively.

Description

An issue was discovered in Vaultize Enterprise File Sharing 17.05.31. There is improper authorization when listing the history of another user via a modified "vaultize_session_id" value in a cookie.

References

Community reviews

Loading reviews…