CVE-2026-1697: Use of unsecure cookies for GraphicalData web service and WebClient web app

Published Feb 26, 2026
·
Updated

The Secure and SameSite attribute are missing in the GraphicalData web services and WebClient web app of PcVue in version 12.0.0 through 16.3.3 included.

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

    Disable all OAuth flows for third-party web apps by default (manual enablement is required before deployment if needed). Include checking that each authorized Client has the correct OAuth flow enabled (Authorization Code flow, Authorization Code flow with PKCE, and/or ROPC) as appropriate.

    Third-party web apps (OAuth) OAuth flows = disabled (default) / manually enabled before deployment if required
  2. Configuration

    For PcVue version 12.0.0 through 16.3.3, ensure cookies used by the GraphicalData web services and the WebClient web app include the Secure and SameSite attributes (mitigates risk of exploitation due to missing attributes).

    PcVue GraphicalData web services / WebClient web app (v12.0.0 through 16.3.3) Secure and SameSite cookie attributes = add/ensure present
  3. Configuration

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

    PcVue Web & Mobile features Web & Mobile features installation location = Web Server only (if required); do not install if not required
  4. Compensating control

    Locate control system networks and remote devices behind firewalls and isolate them from business networks; minimize network exposure so control system devices/systems are not accessible from insecure networks.

  5. Compensating control

    When remote access is required, use secure methods such as VPNs; ensure VPNs are updated to the most current version available and recognize VPN security depends on the security of connected devices.

  6. Operational

    To verify the patch is applied correctly: check the File version property of ./bin/Modules/WebDeployment/WebDeploymentConsole.exe on the IIS Web server matches the deployed release or later, and ensure any earlier release is no longer used. Then uninstall the Web Server, update the WDC, and re-deploy the Web Server.

Event History

Feb 26, 2026
CVE Published
via MITRE·07:57 AM
Data Sourced
via MITRE·07:57 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·08:16 AM
DescriptionSeverityWeaknessAffected Software
Feb 12, 58202
Event
via NVD·03:14 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-1697?

CVE-2026-1697 is considered a medium severity vulnerability due to the lack of secure cookies.

2

How do I fix CVE-2026-1697?

To fix CVE-2026-1697, ensure the Secure and SameSite attributes are implemented for cookies in your configurations.

3

What software versions are affected by CVE-2026-1697?

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

4

What issues does CVE-2026-1697 pose for users?

CVE-2026-1697 can expose user sessions to risks such as cross-site scripting and session hijacking.

5

Is there a patch available for CVE-2026-1697?

As of now, check with the PcVue vendor for a patch or update that addresses CVE-2026-1697.

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