Security readout for executives and security teams
Plain-English summary
This CVE lets someone infer whether an email address belongs to a YetiShare account by observing password-reset response timing. It does not indicate account takeover by itself, but it can support phishing, credential-stuffing targeting, and privacy exposure.
Executive priority
Treat as a privacy and attack-enablement issue. Prioritize remediation for internet-facing or customer-facing YetiShare portals, but it is lower urgency than code execution, data theft, or authentication bypass flaws.
Technical view
MFScripts YetiShare 3.5.2 through 4.5.3 reportedly returns from _account_forgot_password.ajax.php in measurably different time depending on whether the submitted email maps to an account. That creates a timing-based account enumeration weakness in the forgot-password workflow.
Likely exposure
Exposure is likely limited to organizations running YetiShare 3.5.2 through 4.5.3 with the forgot-password endpoint reachable, especially public file-sharing portals where user email privacy matters.
Exploitation context
The provided sources do not confirm active exploitation, and CISA KEV status is false. Practical abuse would mainly aid account discovery for follow-on social engineering or credential attacks, not direct system compromise.
Researcher notes
Evidence is sparse: the CVE record names the endpoint, versions, and timing behavior, but provides no CVSS, CWE, confirmed patch, or active exploitation claim. Avoid assuming broader YetiShare versions are affected without vendor confirmation.
Mitigation direction
- Check MFScripts/YetiShare vendor guidance for fixed versions or official remediation.
- Upgrade or replace affected YetiShare versions if vendor guidance identifies a corrected release.
- Make password-reset responses and processing time indistinguishable for existing and non-existing accounts.
- Apply rate limiting and abuse monitoring to password-reset requests.
- Restrict public access to legacy YetiShare instances where business requirements allow.
Validation and detection
- Inventory YetiShare deployments and confirm whether versions are 3.5.2 through 4.5.3.
- Confirm whether _account_forgot_password.ajax.php is publicly reachable.
- Review reset-request logs for repeated email guessing patterns.
- After remediation, verify reset behavior is uniform for valid and invalid accounts.
- Document compensating controls if no vendor fix is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-19805 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://medium.com/%40jra8908/yetishare-3-5-2-4-5-3-multiple-vulnerabilities-2d01d0cd7459CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.