CVE-2026-14867
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 · uneditedCredentials of built-in users are insecurely stored in the User directory of PcVue projects, all versions prior to 17.0.0. A local attacker could retrieve users’ credentials. Active Directory accounts are not affected by this vulnerability.
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 confidencePcVue versions prior to 17.0.0 store built-in user credentials insecurely in plain text or weakly protected form within the User project directory. A local attacker with file system access to the project directory can retrieve these credentials and potentially escalate privileges within the application.
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< 17.0.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 PcVue versionLocate the PcVue installation and check its version number (typically found in the application's About section, installer properties, or installation directory metadata)Affected if Version is prior to 17.0.0 (e.g., 16.x, earlier releases)
-
Locate the User project directoryFind the project directory where PcVue stores user-related project data - this is typically within the PcVue installation folder or a designated projects folderAffected if The User project directory exists and contains user configuration files
-
Inspect credential storage filesExamine files within the User project directory for stored user credentials - look for files containing usernames and passwords in plain text, encoded, or weakly encrypted formsAffected if Credentials are found stored in plain text, base64 encoding, or weak encryption without proper key protection
-
Check file permissions on credential filesVerify file system permissions on the User project directory and credential-containing files to determine if unauthorized local access is possibleAffected if Files are readable by users other than the application administrator
Your environment is affected if PcVue version is below 17.0.0 AND the User project directory contains credential files stored in plain text or weakly protected form accessible to unauthorized local 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.
dbcve · scoped17.0.0
Upgrade to PcVue version 17.0.0 or later which implements secure credential storage. Until upgraded, limit physical and file system access to project directories and monitor for unauthorized access.
17.0.0
- Backup the existing PcVue project, particularly the User directory containing user configurations
- Download PcVue version 17.0.0 or later from the official vendor website (www.pcvue.com)
- Install the new version following the standard upgrade procedure
- After upgrading, verify that built-in user credentials are stored in the secure format
- Confirm that existing user credentials are accessible and functional after the upgrade
- Ensure the User directory permissions are appropriately restricted post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14867 — 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-14867 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