Security readout for executives and security teams
Plain-English summary
YetiShare versions 3.5.2 through 4.5.3 created password reset hashes in a predictable way. An attacker who can trigger password resets may be able to guess a reset hash within hours and set another user's password, causing account takeover.
Executive priority
Treat this as high priority where affected YetiShare instances are public-facing. The business risk is unauthorized account takeover, not just password reset abuse.
Technical view
The flaw is in class.userpeer.php. Password reset hashes are reportedly derived only from microtime, giving insufficient unpredictability. The CVE description states brute forcing can recover a valid hash within a few hours, enabling unauthorized password changes.
Likely exposure
Exposure is limited to organizations running MFScripts YetiShare 3.5.2 through 4.5.3, especially internet-facing instances with password reset enabled.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references exist, and the CVE description says guessing the reset hash is practical within hours.
Researcher notes
Evidence is specific but sparse. The core issue is predictable reset-token generation based only on microtime. Avoid assuming affected products beyond YetiShare 3.5.2 through 4.5.3 or claiming active exploitation without external evidence.
Mitigation direction
- Inventory YetiShare deployments and confirm exact versions.
- Check MFScripts guidance for fixed versions or vendor-approved remediation.
- Restrict or disable public password reset until remediation is confirmed.
- Prioritize administrator and high-value user accounts for review.
- After remediation, force resets for accounts with suspicious reset activity.
Validation and detection
- Confirm whether any instance runs YetiShare 3.5.2 through 4.5.3.
- Review class.userpeer.php reset hash generation in deployed code.
- Check logs for unusual password reset requests or completions.
- Verify vendor remediation replaces predictable reset hashes with strong randomness.
- Confirm exposed reset endpoints are no longer vulnerable after update.
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.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-19735 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
- https://github.com/jra89/CVE-2019-19735CVE 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.