dbcve.org
PcvueApplication · Arcinfo

CVE-2026-1693

HIGH · 7.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 16.3.4 or later.
See remediation →
84/100
Remediation priority · High
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 OAuth grant type Resource Owner Password Credentials (ROPC) flow is still used by the werbservices used by the WebVue, WebScheduler, TouchVue and Snapvue features of PcVue in version 12.0.0 through 16.3.3 included despite being deprecated. It might allow a remote attacker to steal user credentials.

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

The PcVue web services for WebVue, WebScheduler, TouchVue, and Snapvue features in versions 12.0.0 through 16.3.3 continue using the deprecated OAuth Resource Owner Password Credentials (ROPC) grant type. This flow exposes user credentials directly to the application, enabling potential credential theft by remote attackers through interception or phishing.

MitigationReplace the ROPC flow with modern OAuth 2.0 authorization flows such as Authorization Code Flow with PKCE, which does not expose credentials and supports secure token handling. Conduct authentication testing across all affected web services after migration.

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
High
Integrity
None
Availability
None

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

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

  1. Identify PcVue installation and version
    Check the installed PcVue version by reviewing installation directories, program files, or running 'sv' command if available. Common paths: C:\Program Files\PcVue\ or check Windows Programs and Features.
    Affected if Installed version matches >= 12.0.0, <= 15.2.13 OR >= 16.0.0, < 16.3.4
  2. Confirm WebVue service is enabled
    Check if the WebVue web service is running or configured. Look for IIS application pools, Windows services, or configuration files in the PcVue installation directory under WebVue or similar web service folders.
    Affected if WebVue service is installed and running on versions in the affected range
  3. Check for OAuth ROPC configuration
    Examine configuration files (web.config, appsettings.json, or similar) in the WebVue, WebScheduler, TouchVue, or Snapvue service directories for OAuth-related settings, specifically looking for 'grant_type=password' or 'ResourceOwner' or 'ROPC' entries.
    Affected if Configuration files contain ROPC grant type settings or password-based OAuth flows
  4. Verify TouchVue or Snapvue endpoints are exposed
    Check if TouchVue or Snapvue mobile/web endpoints are accessible or configured. Review IIS bindings, virtual directories, or service configuration files for these specific modules.
    Affected if TouchVue or Snapvue modules are enabled on affected versions

Your environment is affected if PcVue version is between 12.0.0-15.2.13 or 16.0.0-16.3.3 AND any of the web services (WebVue, WebScheduler, TouchVue, Snapvue) using OAuth ROPC flow are enabled.

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

Replace the ROPC flow with modern OAuth 2.0 authorization flows such as Authorization Code Flow with PKCE, which does not expose credentials and supports secure token handling. Conduct authentication testing across all affected web services after migration.

Recommended fix Moderate confidence

PcVue 16.3.4 or later (also 15.2.14 or later if staying on the 15.x branch)

  1. 1. Identify the current PcVue installation version by checking the application or system information.
  2. 2. Back up the current PcVue configuration, databases, and any custom settings before proceeding with the upgrade.
  3. 3. Download PcVue version 16.3.4 or a later stable release from the official vendor website (www.pcvue.com) or your authorized distribution channel.
  4. 4. Install the new version on a test system first to verify compatibility with your existing configurations and integrations.
  5. 5. After successful testing, schedule a maintenance window and deploy the upgrade to production systems.
  6. 6. Verify that the WebVue, WebScheduler, TouchVue, and Snapvue features are functioning correctly after the upgrade.
  7. 7. Confirm that the deprecated ROPC OAuth flow is no longer in use by reviewing the authentication configuration.
Caveat Review release notes for version 16.3.4 for any configuration or feature changes that may affect existing deployments

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

Fix this in Pcvue Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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