CVE-2019-19805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited_account_forgot_password.ajax.php in MFScripts YetiShare 3.5.2 through 4.5.3 takes a different amount of time to return depending on whether an email address is configured for the account name provided. This can be used by an attacker to enumerate accounts by guessing email addresses.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe forgot password endpoint in YetiShare exhibits a time-based side channel that reveals whether an email address is registered. When a valid account is provided, the system performs additional operations (such as generating a reset token and sending an email), causing a measurable delay compared to invalid accounts. Attackers can automate requests with different email addresses and infer account existence from response times.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.5.2, <= 4.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify YetiShare installation existsCheck your web root for the YetiShare application directory (commonly 'yeti-share', 'yeti', or similar naming). Look for index.php or core configuration files that indicate a YetiShare installation.Affected if YetiShare is installed on the server in any form.
-
Identify installed YetiShare versionLocate the version file or configuration. Common locations include: a VERSION file in the root directory, version defined in a config file, or displayed in the admin footer. Compare the version number against the affected range: 3.5.2 through 4.5.3.Affected if The installed version falls within >=3.5.2 and <=4.5.3.
-
Confirm forgot password endpoint is accessibleNavigate to the password reset page in your YetiShare installation (typically /forgot-password, /user/password-reset, or similar URL path). Verify the endpoint responds and accepts email address input.Affected if The forgot password functionality is publicly accessible and operational.
-
Test for response timing differentialSend multiple password reset requests with a known-unregistered email address and record response times. Then send requests with a known-registered email address. Compare average response times between the two. Use automated tooling to measure millisecond differences across multiple attempts.Affected if Response times for registered emails are consistently and measurably longer than for unregistered emails.
Your environment is affected if YetiShare versions 3.5.2 through 4.5.3 are installed, the forgot password endpoint is accessible, and timing analysis shows a measurable difference in response latency between registered and unregistered email addresses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement consistent response timing in the password reset function by processing both valid and invalid accounts identically, or by adding a fixed delay to ensure uniform response times regardless of account validity.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data