CVE-2018-14776
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 · uneditedClick Studios Passwordstate before 8.3 Build 8397 allows XSS by authenticated users via an uploaded HTML document.
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 confidenceClick Studios Passwordstate before version 8.3 Build 8397 contains a stored Cross-Site Scripting (XSS) vulnerability. Authenticated users can upload HTML documents containing malicious JavaScript code, which executes when other users view the uploaded file.
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<= 8.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 Passwordstate installation and versionLocate the Passwordstate installation directory and check the application version information, typically found in the About section of the web interface or in assembly metadata files within the installation folderAffected if The installed version is 8.3 or earlier, or the build number is unknown but the version displays as 8.3
-
Check the build numberDetermine the exact build number of the installed Passwordstate instance. This is usually displayed in the web interface footer, in the application settings, or in version information files within the installation directoryAffected if The build number is lower than 8397, or the build number cannot be determined but the version is 8.3
-
Verify HTML file upload capabilityCheck whether the HTML document upload feature is enabled in Passwordstate. This may be configurable in the administrative settings under document or file upload options, or by reviewing the application's configuration filesAffected if HTML file uploads are permitted and the user role assignments allow authenticated users to upload documents
-
Review uploaded HTML filesInspect the document storage location for any uploaded HTML files. Examine the content of these files for suspicious script tags, JavaScript code, or iframe elements that could indicate exploitation attemptsAffected if HTML files containing embedded JavaScript or external resource references are present in the system
A system is affected if Passwordstate version is 8.3 with a build number below 8397 and HTML file upload functionality is available to authenticated 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 Passwordstate to version 8.3 Build 8397 or later. If immediate upgrade is not possible, implement HTML content sanitization on file uploads and consider restricting or disabling HTML file uploads until the patch can be applied.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14776 — 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-2018-14776 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