dbcve.org
PcvueApplication · Arcinfo

CVE-2026-1697

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 16.3.4 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Secure and SameSite attribute are missing in the GraphicalData web services and WebClient web app of PcVue in version 12.0.0 through 16.3.3 included.

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 confidence

The GraphicalData web services and WebClient web app in PcVue versions 12.0.0 through 16.3.3 are missing the Secure and SameSite cookie attributes. This allows cookies to potentially be transmitted over insecure HTTP connections and increases susceptibility to cross-site request forgery attacks.

MitigationConfigure the Secure flag and SameSite attribute (typically set to 'Strict' or 'Lax') for all session cookies in the GraphicalData web services and WebClient web app configuration.

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
PcvueApplication
Affected:>= 12.0.0, <= 15.2.13>= 16.0.0, < 16.3.4

CVSS 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PcVue version
    Check the installed PcVue version by looking in the installation directory or Windows Programs and Features. Look for version information in the application properties or about dialog.
    Affected if Version is >= 12.0.0 and <= 15.2.13, or >= 16.0.0 and < 16.3.4
  2. Verify GraphicalData web service is in use
    Check if the GraphicalData web service is enabled and accessible. Look for GraphicalData service endpoints in the web server configuration files or IIS if hosted on IIS.
    Affected if GraphicalData web service is enabled and running in the environment
  3. Verify WebClient web app is in use
    Check if the WebClient web application is deployed and accessible. Look for WebClient configuration in the installation directory or IIS sites.
    Affected if WebClient web app is deployed and accessible
  4. Inspect cookie headers from web services
    Use browser developer tools or a network capture tool (like Wireshark or curl) to capture HTTP responses from the GraphicalData and WebClient endpoints. Examine the Set-Cookie headers for the presence of Secure and SameSite attributes.
    Affected if Cookies are set without the Secure flag or without a SameSite attribute (or SameSite is set to None without Secure)
  5. Check cookie configuration files
    Inspect the configuration files for the GraphicalData web service and WebClient web app in the PcVue installation directory for cookie settings. Look for session configuration or web.config files.
    Affected if Cookie configuration lacks Secure and SameSite attributes or these are set to insecure values

The environment is affected if PcVue version is within the vulnerable range AND either GraphicalData web services or WebClient web app is in use AND cookies are missing Secure or SameSite attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 16.3.4 or later
Fixed in 16.3.4
Interim mitigation

Configure the Secure flag and SameSite attribute (typically set to 'Strict' or 'Lax') for all session cookies in the GraphicalData web services and WebClient web app configuration.

Recommended fix High confidence

16.3.4 or later

  1. Verify current Pcvue installation version using the system information panel or version check utility
  2. Download Pcvue version 16.3.4 or later from the official vendor (www.pcvue.com)
  3. Review upgrade documentation and release notes for version 16.3.4
  4. Perform a complete backup of the current Pcvue installation including configuration files, projects, and databases
  5. Execute the installer for version 16.3.4 or later, following the standard upgrade procedure
  6. Verify the upgrade was successful by checking the new version number
  7. Confirm the Secure and SameSite attributes are now properly set on cookies for GraphicalData web services and WebClient web app

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pcvue Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1697 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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