CVE-2019-19737
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 · uneditedMFScripts YetiShare 3.5.2 through 4.5.3 does not set the SameSite flag on session cookies, allowing the cookie to be sent in cross-site requests and potentially be used in cross-site request forgery attacks.
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 confidenceMFScripts YetiShare versions 3.5.2 through 4.5.3 fails to set the SameSite attribute on session cookies, allowing them to be transmitted in cross-site requests. This enables attackers to potentially hijack authenticated sessions or perform CSRF attacks by tricking users into making unintended requests to the application.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify YetiShare versionCheck the version.php file in the application root directory, or log into the admin panel and look at the Dashboard or About section for the installed version number.Affected if Version falls between 3.5.2 and 4.5.3 inclusive
-
Inspect session cookie headersLog into the application and use browser developer tools (F12). In the Network tab, examine the Set-Cookie headers from the server response. Look for the session cookie and check if it contains a SameSite=Strict or SameSite=Lax attribute.Affected if The session cookie Set-Cookie header does not include any SameSite attribute
-
Check PHP session configurationLocate the PHP session configuration file (php.ini) or check the application's session handling code for the session.cookie_samesite PHP setting. If available, run: php -i | grep session.cookie_samesiteAffected if session.cookie_samesite is not set to Strict or Lax, or is set to None without Secure flag
-
Review application session codeExamine the session initialization code in YetiShare, typically in include/config.php or similar core files. Look for session_set_cookie_params() calls and check if the SameSite parameter is defined.Affected if session_set_cookie_params() is called without a SameSite parameter, or the parameter is empty/null
You are affected if your installed YetiShare version is between 3.5.2 and 4.5.3 AND your session cookies are missing the SameSite attribute in their Set-Cookie headers.
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 dataConfigure session cookies to include the SameSite=Strict or SameSite=Lax attribute in the application's cookie handling code or server configuration to prevent cross-site cookie transmission.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19737 — 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-19737 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