CVE-2019-13380
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 · uneditedKEYNTO Team Password Manager 1.5.0 allows XSS because data saved from websites is mishandled in the online vault.
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 · moderate confidenceCross-site scripting vulnerability in KEYNTO Team Password Manager 1.5.0 where data saved from websites is not properly sanitized before being displayed in the online vault. An attacker could inject malicious scripts through saved website data that would execute in the context of other users viewing the vault.
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= 1.5.0CVSS 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.0/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 the installed version of Keynto Team Password ManagerLocate the version information in the application admin panel, About page, or installation files. Common locations include the login page footer, admin dashboard, or configuration files.Affected if The installed version is exactly 1.5.0
-
Verify access to the online vault featureLog in as a standard user and confirm the vault functionality is accessible. Check if users can save or view website credentials through the vault interface.Affected if The vault feature is enabled and users can save or view saved website data
-
Inspect saved website data entriesNavigate to the vault, select any entry containing saved website data, and view the details panel where credentials and website information are displayed.Affected if Saved website data entries exist in the vault and are displayed in the web interface
-
Test for reflected content in vault displayExamine the HTML source of a vault entry page containing saved website data. Look for unescaped characters such as <, >, or quotes in the displayed content.Affected if The rendered HTML shows raw tags or unescaped characters from saved data rather than encoded output
A user is affected if Keynto Team Password Manager version 1.5.0 is installed and the vault feature with saved website data is in use, as the injected script would execute when other users view that data in the vault interface.
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 proper input validation and output encoding for all data displayed from the vault. Use context-appropriate sanitization (HTML encoding, URL encoding) when rendering saved credentials or website data in the web interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13380 — 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-13380 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