CVE-2026-1693: Use of vulnerable Resource Owner Password Credentials flow
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.2.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.3.4 - Configuration
Ensure all OAuth flows are disabled for third-party web apps unless the deployment specifically requires them; if required, manually enable only the necessary flow per authorized Client.
OAuth (third-party web apps) OAuth flows for third-party web apps = disabled by default; manually enable only if required - Configuration
In the patched Web Deployment Console (WDC) settings, verify the Authorization Code flow is correctly enabled or disabled for each authorized Client.
OAuth Authorization Code flow OAuth grant type (Authorization Code flow) = enabled/disabled per authorized Client - Configuration
In the patched Web Deployment Console (WDC) settings, verify the Authorization Code flow with PKCE is correctly enabled or disabled for each authorized Client.
OAuth Authorization Code flow with PKCE OAuth grant type (Authorization Code flow with PKCE) = enabled/disabled per authorized Client - Configuration
In the patched Web Deployment Console (WDC) settings, verify the ROPC flow is correctly enabled or disabled for each authorized Client; for systems that do not depend on OAuth ROPC, disable it to reduce exploitation risk.
OAuth Resource Owner Password Credentials (ROPC) flow OAuth grant type (Resource Owner Password Credentials flow) = enabled/disabled per authorized Client - Compensating control
Locate control system networks and remote devices behind firewalls and isolate them from business networks; minimize network exposure for all control system devices/systems and ensure they are not accessible from insecure networks.
- Compensating control
When remote access is required, use secure methods such as VPNs (and recognize VPN security depends on connected devices); update VPNs to the most current version available.
- Operational
Verify the Web Deployment Console (WDC) installation by checking that the File version property of ./bin/Modules/WebDeployment/WebDeploymentConsole.exe matches the deployed release or later, and ensure any earlier release is no longer used.
- Operational
If you do not require the Web & Mobile features, do not install them. If required, install them only on the Web Server.
- Operational
Follow the verification steps: uninstall the Web Server, update the Web Deployment Console (WDC), then re-deploy the Web Server.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-1693?
CVE-2026-1693 is classified as a medium severity vulnerability due to the use of a deprecated authorization flow.
How do I fix CVE-2026-1693?
To fix CVE-2026-1693, you should update your PcVue software to a version that does not use the Resource Owner Password Credentials flow.
Which versions of PcVue are affected by CVE-2026-1693?
CVE-2026-1693 affects PcVue versions 12.0.0 through 16.3.3.
What features of PcVue are impacted by CVE-2026-1693?
CVE-2026-1693 impacts the WebVue, WebScheduler, TouchVue, and Snapvue features of PcVue.
Is the Resource Owner Password Credentials flow secure in the context of CVE-2026-1693?
No, the Resource Owner Password Credentials flow is considered insecure and deprecated, leading to vulnerabilities like CVE-2026-1693.