dbcve.org
PcvueApplication · Arcinfo

CVE-2026-1695

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

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
An XSS vulnerability affects the OAuth web services used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It might allow a remote attacker to trick a legitimate user into loading content from another site upon unsuccessful user authentication on an unknown application (unknown client_id). This vulnerability only affects the error page of the OAuth server.

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 confidence

PcVue versions 12.0.0-16.3.3 contain a reflected XSS vulnerability in the OAuth server's error page. When user authentication fails due to an unknown client_id, the error response does not properly sanitize output, allowing injection of malicious scripts via the error page that could exfiltrate session tokens or perform actions as the authenticated user.

MitigationUpgrade PcVue to version 16.3.4 or later. Until then, disable or restrict access to the affected OAuth endpoints for WebVue, WebScheduler, TouchVue, and SnapVue features, and implement WAF rules to filter XSS payloads in OAuth error responses.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify PcVue installation version
    Locate the installed PcVue version by checking the program files directory, or run: reg query 'HKLM\SOFTWARE\WOW6432Node\PcVue' /v Version (or HKLM\SOFTWARE\PcVue\Version). Alternatively, right-click the main executable and view Properties > Details for FileVersion.
    Affected if Installed version is between 12.0.0 and 15.2.13 inclusive, or between 16.0.0 and 16.3.3 inclusive
  2. Confirm OAuth features are enabled
    Check if any of the following web interfaces are installed and running: WebVue, WebScheduler, TouchVue, or SnapVue. Look for corresponding IIS sites, application pools, or check the PcVue installation folder for \WebVue\, \WebScheduler\, \TouchVue\, or \SnapVue\ subdirectories.
    Affected if One or more OAuth-enabled web features (WebVue, WebScheduler, TouchVue, SnapVue) are installed and accessible
  3. Verify OAuth endpoint accessibility
    Identify the OAuth server endpoint URL (typically https://servername/oauth/authorize or similar). Attempt to trigger an authentication error by sending a request with an invalid or unknown client_id parameter, for example: GET /oauth/authorize?response_type=code&client_id=invalidclient123&redirect_uri=https://example.com
    Affected if The OAuth endpoint responds to authentication requests and returns an error page
  4. Inspect OAuth error page for XSS vulnerability
    Send a crafted request with a malicious script in the client_id parameter, for example: /oauth/authorize?response_type=code&client_id=<script>alert(1)</script>&redirect_uri=https://example.com. Examine the returned HTML error page to see if the script is reflected without encoding.
    Affected if The error page reflects the client_id value (or any parameter) back into the HTML output without proper sanitization or encoding

You are affected if your installed PcVue version falls within 12.0.0-15.2.13 or 16.0.0-16.3.3 AND you have any OAuth-enabled web interface (WebVue, WebScheduler, TouchVue, or SnapVue) exposed, and the OAuth error page reflects unsanitized input.

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

Upgrade PcVue to version 16.3.4 or later. Until then, disable or restrict access to the affected OAuth endpoints for WebVue, WebScheduler, TouchVue, and SnapVue features, and implement WAF rules to filter XSS payloads in OAuth error responses.

Recommended fix High confidence

16.3.4

  1. Obtain PcVue version 16.3.4 from the official vendor (www.pcvue.com)
  2. Follow the vendor's standard upgrade procedure to update from your current version to 16.3.4
  3. After upgrading, verify that the OAuth services (WebVue, WebScheduler, TouchVue, SnapVue) function correctly
  4. Test that the OAuth error page no longer reflects unsanitized input

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

Fix this in Pcvue Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1695 — 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-1695 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