CVE-2018-10210VulnerabilityPublished 25 Apr 2018Updated 30 May 2025

CVE-2018-10210: n/a

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Medium

Rated Medium 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

Disclosed: evidence found.
CVE published 25 Apr 2018
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =17.05.31	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement the following specific measures: 1) Modify the password-reset feature to provide generic, non-distinguishing responses regardless of whether the user exists or not. For example, always respond with a message like 'If the email is registered, you will receive a reset link,' to avoid revealing user existence. 2) Implement rate limiting and CAPTCHA challenges on password reset requests to prevent automated enumeration attempts. 3) Monitor logs for unusual password reset activity that may indicate enumeration attempts. 4) Encourage or enforce multi-factor authentication (MFA) for user accounts to reduce the impact of compromised credentials obtained through enumeration-assisted attacks. 5) If possible, upgrade to a newer version of Vaultize Enterprise File Sharing where this issue is addressed or apply vendor patches once available. 6) Conduct user awareness training to help users recognize phishing attempts that may follow enumeration. These targeted mitigations go beyond generic advice by focusing on hardening the password reset workflow and detecting enumeration behaviors.

Description

An issue was discovered in Vaultize Enterprise File Sharing 17.05.31. Enumeration of users is possible through the password-reset feature.

Impact

For European organizations using Vaultize Enterprise File Sharing 17.05.31, this vulnerability poses a moderate security risk. User enumeration can significantly aid attackers in mapping out valid user accounts within an organization, which is a critical first step in targeted attacks. Once valid users are identified, attackers can launch phishing campaigns tailored to those users or attempt password guessing and credential stuffing attacks. This can lead to unauthorized access to sensitive files and data, potentially resulting in data breaches, intellectual property theft, or compliance violations under regulations such as GDPR. While the vulnerability itself does not grant direct access or compromise system integrity, it lowers the barrier for attackers to conduct more effective social engineering or brute force attacks. Enterprises relying on Vaultize for secure file sharing should be aware that their user base could be exposed to enumeration, increasing the risk of account compromise and subsequent data leakage or disruption of services.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 14:56 UTC

Technical details

References

Community reviews

Related threats