CVE-2019-19461
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 · uneditedPost-authentication Stored XSS in Team Password Manager through 7.93.204 allows attackers to steal other users' credentials by creating a shared password with HTML code as the title.
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 confidenceAuthenticated users can inject malicious HTML/JavaScript code into the title field of shared passwords in Team Password Manager through version 7.93.204. When other users view these password entries, the stored XSS payload executes in their browser context, enabling credential theft and session hijacking.
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<= 7.93.204CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 installed version of Team Password ManagerLocate the version number in the application interface (typically found in the admin panel, footer, or 'About' section) or check the application's configuration files or database for the version metadataAffected if The installed version is 7.93.204 or lower
-
Verify access to password management featuresConfirm your user account has access to create or edit password entries - the vulnerability requires authenticated access to the password title field functionalityAffected if You have authenticated access to the password entry creation or editing interface
-
Examine stored password entries for suspicious title contentQuery the passwords table in the database or review password entries through the web interface, specifically inspecting the 'title' or 'name' field of password entries for HTML or JavaScript code patterns such as <script>, <img onerror>, javascript:, or other XSS vectorsAffected if Any password entry title field contains unescaped HTML tags, script elements, or JavaScript event handlers
-
Test for XSS in your own environment (non-production only)If authorized, create a test password entry with a benign XSS payload in the title field (e.g., <img src=x onerror=alert(1)>), then view that entry as a different user account to confirm the payload executesAffected if The injected payload executes and triggers JavaScript when the password entry is viewed in a browser
You are affected if your Team Password Manager version is 7.93.204 or lower AND you have password entries in the database with unescaped HTML/JavaScript in their title fields that could execute when viewed by other users.
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 dataUpgrade to a version beyond 7.93.204 that implements proper input validation and output encoding for password title fields, or apply output escaping/validation on the display layer to neutralize stored XSS vectors.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19461 — 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-19461 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