CVE-2026-1693: Use of vulnerable Resource Owner Password Credentials flow

Published Feb 26, 2026
·
Updated

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

3 affected components
PcVue PcVue>=12.0.0<=16.3.3
Arcinfo Pcvue>=12.0.0<=15.2.13
Arcinfo Pcvue>=16.0.0<16.3.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.2.14
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.3.4
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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.

  8. 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.

  9. 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.

  10. Operational

    If you do not require the Web & Mobile features, do not install them. If required, install them only on the Web Server.

  11. Operational

    Follow the verification steps: uninstall the Web Server, update the Web Deployment Console (WDC), then re-deploy the Web Server.

Event History

Feb 26, 2026
CVE Published
via MITRE·07:56 AM
Data Sourced
via MITRE·07:56 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·08:16 AM
DescriptionSeverityWeaknessAffected Software
Jul 4, 58164
Event
via NVD·08:54 PM

Frequently Asked Questions

1

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.

2

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.

3

Which versions of PcVue are affected by CVE-2026-1693?

CVE-2026-1693 affects PcVue versions 12.0.0 through 16.3.3.

4

What features of PcVue are impacted by CVE-2026-1693?

CVE-2026-1693 impacts the WebVue, WebScheduler, TouchVue, and Snapvue features of PcVue.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203