CVE-2026-3107
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 · uneditedStored Cross-Site Scripting (XSS) in Teampass versions prior to 3.1.5.16, affecting the password manager's password import functionality at the endpoint 'redacted/index.php?page=items'. The application fails to properly sanitize and encode user-input data during the import process, allowing malicious JavaScript payloads to be persistently stored in the database. When other users view the imported passwords, the payload is automatically executed in their browsers, resulting in a stored XSS condition at the endpoint 'redacted/index.php?page=items'. Exploiting this vulnerability allows an attacker to execute arbitrary JavaScript code in the context of multiple users and the administrator, which can lead to session hijacking, credential theft, privilege abuse, and compromise of application integrity.
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 confidenceStored XSS vulnerability in Teampass password import functionality allows attackers to inject malicious JavaScript payloads through the import process. The payloads are persistently stored in the database and execute automatically when other users view the imported passwords at the items page, enabling session hijacking and credential theft.
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.1.5.16, < 3.1.5.24CVSS 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 Teampass versionAccess the Teampass admin panel and navigate to 'About' or 'Settings' page, or check the version.php file in the installation directory. Alternatively, inspect the response headers or footer of the web interface for the version number.Affected if Version is 3.1.5.16 or higher but lower than 3.1.5.24
-
Review password import feature usage logsCheck Teampass audit logs or access logs for entries related to 'import' functionality, particularly CSV or password import operations. Look for the import feature under Items > Import passwords.Affected if Password import functionality has been used and the version falls within the affected range
-
Inspect database for suspicious entries in password fieldsQuery the Teampass database (typically table 'items' or similar) and examine the 'password' or 'description' fields for HTML script tags, JavaScript event handlers, or encoded payloads. Look for patterns like '<script>', 'javascript:', 'onerror=', 'onload='.Affected if Any password or description fields contain unencoded HTML/JavaScript content indicating exploitation
-
Check item list page for unexpected script executionAs a test, view the items page in Teampass (where imported passwords are displayed) using a browser with JavaScript disabled or using developer tools to inspect page source. Look for any script tags or event handlers in password field outputs.Affected if Output contains raw HTML or script tags instead of sanitized text when viewing imported items
The environment is affected if Teampass version is 3.1.5.16 or higher but lower than 3.1.5.24 and the password import feature has been used, or if XSS payloads are found in the database.
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.
dbcve · scoped3.1.5.24
Upgrade to Teampass version 3.1.5.16 or later. Additionally, implement proper input validation and output encoding for all user-supplied data in the password import and display functionality.
Teampass 3.1.5.24
- Backup the Teampass database and files before proceeding with any changes
- Download Teampass version 3.1.5.24 or a later stable release from the official Teampass repository (github.com/nilsteampassnet/TeamPass)
- Follow the official Teampass upgrade instructions to apply the update
- Verify the upgrade was successful by logging into the application
- Confirm the password import functionality at items endpoint no longer executes unsanitized JavaScript
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3107 — 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-2026-3107 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