CVE-2019-19736
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 HttpOnly flag on session cookies, allowing the cookie to be read by script, which can potentially be used by attackers to obtain the cookie via cross-site scripting.
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 HttpOnly flag on session cookies during session creation. Without this flag, session cookies are accessible to client-side JavaScript, enabling attackers to potentially steal session identifiers via existing cross-site scripting (XSS) vulnerabilities.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify YetiShare installationLocate the YetiShare installation by searching for characteristic files such as 'init.php', 'config.php', or the '/_libs/' directory structure typical of this PHP application. Check web root for folders named 'yetishare' or 'mfscripts'.Affected if YetiShare is not found in the environment - not applicable
-
Determine installed YetiShare versionOpen the version file or check the admin dashboard footer for the version number. Common locations include a 'version' file in the root directory or the '/admin' area login page footer.Affected if Installed version is outside the 3.5.2 to 4.5.3 range - not affected
-
Inspect session cookie HttpOnly flagLog into the YetiShare application and use browser developer tools (Application tab > Cookies) or a command-line tool like curl to capture response headers. Examine the session cookie (typically named 'PHPSESSID' or similar) for the HttpOnly attribute in the Set-Cookie header.Affected if The session cookie lacks the HttpOnly attribute - VULNERABLE
-
Verify cookie is a session identifierConfirm the cookie being tested is the actual session identifier by checking its name, expiration behavior (session scope), and ensuring it persists across page loads.Affected if No session identifier cookie is present or cookie is properly protected - not affected
A user is affected if their YetiShare installation falls within version 3.5.2 through 4.5.3 AND the session cookie lacks the HttpOnly flag, especially if an XSS vulnerability exists.
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 the application or web server to set the HttpOnly attribute on all session cookies to prevent JavaScript access.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19736 — 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-19736 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