Metrics
Affected Vendors & Products
No advisories yet.
Solution
Harden the configuration Who should apply this recommendation: All users To reduce the risk of exploitation, ARC Informatique strongly recommends implementing the following defensive measures: * Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from insecure networks. * Locate control system networks and remote devices behind firewalls and isolate them from business networks. * When remote access is required, use secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as its connected devices. Uninstall the Web Server Who should apply this recommendation: All users not using the affected component If your system does not require the use of the Web & Mobile features, you should make sure not to install them. If your system requires the use of the Web & Mobile features, they should be installed only on the Web Server. See the product help related to the installation for more information. Update the Web Deployment Console (WDC) and re deploy the Web Server Who should apply this recommendation: All users running affected components. Install a patched release of the Web Deployment Console (WDC) on the IIS Web server and use it to re-deploy the Web Site. Some settings might need to be updated if third-party web apps or services depend on the OAuth ROPC flow. In a patched release of the WDC, new settings are available for each authorized Client to enable or disable: * The Authorization Code flow * The Authorization Code flow with PKCE * The Resource Owner Password Credentials (ROPC) flow By default, all the OAuth flows are now disabled for third-party web apps and need to be manually enabled before deployment if required. To verify that the patch is applied correctly, you must check that: * The File version property of the file ./bin/Modules/WebDeployment/WebDeploymentConsole.exe matches the deployed release or later, and ensure that any earlier release is no longer used; * Web Sites have been redeployed; * OAuth flow are correctly set for each authorized Client. Available patches: Patch provided in: * PcVue 16.3.4 (16.3.4902.3112) Patch planned in: * PcVue 15.2.14
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://www.pcvue.com/security/#SB2026-2 |
|
Thu, 26 Feb 2026 08:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Use of vulnerable Resource Owner Password Credentials flow | |
| First Time appeared |
Arcinfo
Arcinfo pcvue |
|
| Weaknesses | CWE-1390 CWE-477 |
|
| CPEs | cpe:2.3:a:arcinfo:pcvue:*:*:*:*:*:*:*:* cpe:2.3:a:arcinfo:pcvue:12.0.0:*:*:*:*:*:*:* |
|
| Vendors & Products |
Arcinfo
Arcinfo pcvue |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: arcinfo
Published:
Updated: 2026-02-26T07:56:10.326Z
Reserved: 2026-01-30T08:37:34.459Z
Link: CVE-2026-1693
No data.
Status : Received
Published: 2026-02-26T08:16:18.490
Modified: 2026-02-26T08:16:18.490
Link: CVE-2026-1693
No data.
OpenCVE Enrichment
No data.