CVE-2026-1694 (GCVE-0-2026-1694)

Vulnerability from cvelistv5 – Published: 2026-02-26 07:56 – Updated: 2026-02-26 14:22
VLAI?
Title
Server configuration details in HTTP headers
Summary
HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.
Severity ?
2.3 (Low)
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:U/RE:M/U:Clear
CWE
  • CWE-201 - Insertion of Sensitive Information into Sent Data
Assigner
References
Impacted products
Vendor Product Version
arcinfo PcVue Affected: 16.0.0 , ≤ 16.3.3 (cpe)
Affected: 15.0.0 , ≤ 15.2.13 (cpe)
Affected: 12.0.0 (cpe)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-1694",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-02-26T14:22:01.724842Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-02-26T14:22:11.880Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "modules": [
            "WebVue",
            "WebScheduler",
            "TouchVue",
            "SnapVue",
            "Web services"
          ],
          "product": "PcVue",
          "vendor": "arcinfo",
          "versions": [
            {
              "lessThanOrEqual": "16.3.3",
              "status": "affected",
              "version": "16.0.0",
              "versionType": "cpe"
            },
            {
              "lessThanOrEqual": "15.2.13",
              "status": "affected",
              "version": "15.0.0",
              "versionType": "cpe"
            },
            {
              "status": "affected",
              "version": "12.0.0",
              "versionType": "cpe"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:arcinfo:pcvue:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "16.3.3",
                  "versionStartIncluding": "16.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:arcinfo:pcvue:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "15.2.13",
                  "versionStartIncluding": "15.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:arcinfo:pcvue:12.0.0:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ],
          "operator": "OR"
        }
      ],
      "datePublic": "2026-02-25T23:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.\u003cbr\u003e"
            }
          ],
          "value": "HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration."
        }
      ],
      "exploits": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "No POC available."
            }
          ],
          "value": "No POC available."
        },
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Not known to be exploited"
            }
          ],
          "value": "Not known to be exploited"
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "YES",
            "Recovery": "USER",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "HIGH",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 2.3,
            "baseSeverity": "LOW",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "NONE",
            "providerUrgency": "CLEAR",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "LOW",
            "subIntegrityImpact": "NONE",
            "userInteraction": "PASSIVE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:U/RE:M/U:Clear",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "MODERATE"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "CNA",
              "version": "2.0.3"
            },
            "type": "ssvc"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-201",
              "description": "CWE-201 Insertion of Sensitive Information into Sent Data",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-02-26T07:56:57.048Z",
        "orgId": "87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932",
        "shortName": "arcinfo"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://www.pcvue.com/security/#SB2026-2"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cb\u003e\u003c/b\u003e\n\n\u003cb\u003eHarden the configuration\u003c/b\u003e\u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e All users\u003cbr\u003e\n\nTo reduce the risk of exploitation, ARC Informatique strongly recommends implementing the following defensive measures:\n\n\u003cul\u003e\u003cli\u003eMinimize network exposure for all control system devices and/or systems, and ensure they are not accessible from insecure networks.\u003c/li\u003e\u003cli\u003eLocate control system networks and remote devices behind firewalls and isolate them from business networks.\u003c/li\u003e\u003cli\u003eWhen 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.\u003c/li\u003e\u003c/ul\u003e\u003cbr\u003e\u003cb\u003eUninstall the Web Server\u003c/b\u003e \u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e All users \u003cb\u003enot \u003c/b\u003eusing the affected component \u003cbr\u003e\u003cbr\u003eIf your system does not require the use of the Web \u0026amp; Mobile features, you should make sure not to install them. If your system requires the use of the Web \u0026amp; Mobile features, they should be installed only on the Web Server.\u003cbr\u003eSee the product help related to the installation for more information.\n\n\u003cbr\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eUpdate IIS configuration \u2013 manually update HTTP headers\u003c/b\u003e\u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e \n\nAll users running affected components.\n\n\u003cbr\u003e\u003cbr\u003eAs a quick mitigation for the unnecessary and missing HTTP headers, you can disable default headers and add secure HTTP headers for all requests. Those options can be set via the web.config file located on the IIS by following those steps:\u003cbr\u003e\u003col\u003e\u003cli\u003eOpen the file \u003ci\u003eC:\\inetpub\\\u0026lt;SV Website\u0026gt;\\web.config\u003c/i\u003e\u003c/li\u003e\u003cli\u003eAdd the following entries to the section \u003ci\u003ecustomHeaders\u003c/i\u003e, which are the recommendations from the official OWASP site:\u003cbr\u003e\u0026lt;remove name=\"X-Powered-By\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"X-Frame-Options\" value=\"DENY\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"X-XSS-Protection\" value=\"0\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"X-Content-Type-Options\" value=\"nosniff\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"X-DNS-Prefetch-Control\" value=\"off\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"Cross-Origin-Opener-Policy\" value=\"same-origin\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"Cross-Origin-Embedder-Policy\" value=\"require-corp\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"Cross-Origin-Resource-Policy\" value=\"same-site\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"Referrer-Policy\" value=\"strict-origin-when-cross-origin\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"Strict-Transport-Security\" value=\"max-age=63072000; includeSubDomains; preload\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\"Permissions-Policy\" value=\"geolocation=(), camera=(), microphone=()\" /\u0026gt;\u003c/li\u003e\u003c/ol\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eUpdate the Web Deployment Console (WDC) and re deploy the Web Server\u003c/b\u003e\u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e \n\nAll users running affected components.\n\n\u003cbr\u003e\u003cbr\u003eInstall 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.\u003cbr\u003e\u003cbr\u003eIn a patched release of the WDC, new settings are available for each authorized Client to enable or disable:\u003cbr\u003e\u003cul\u003e\u003cli\u003eThe Authorization Code flow\u003c/li\u003e\u003cli\u003eThe Authorization Code flow with PKCE\u003c/li\u003e\u003cli\u003eThe Resource Owner Password Credentials (ROPC) flow\u003c/li\u003e\u003c/ul\u003eBy default, all the OAuth flows are now disabled for third-party web apps and need to be manually enabled before deployment if required.\u003cbr\u003e\u003cbr\u003eTo verify that the patch is applied correctly, you must check that:\u003cbr\u003e\u003cul\u003e\u003cli\u003eThe \u003ci\u003eFile version\u003c/i\u003e property of the file \u003ci\u003e./bin/Modules/WebDeployment/WebDeploymentConsole.exe\u003c/i\u003e matches the deployed release or later, and ensure that any earlier release is no longer used;\u003c/li\u003e\u003cli\u003eWeb Sites have been redeployed;\u003c/li\u003e\u003cli\u003eOAuth flow are correctly set for each authorized Client.\u003c/li\u003e\u003c/ul\u003e\u003cbr\u003e\n\n\u003cb\u003e\u003c/b\u003e\n\n\u003cb\u003eAvailable patches:\u003c/b\u003e\u003cbr\u003ePatch provided in:\u003cbr\u003e\u003cul\u003e\u003cli\u003ePcVue 16.3.4 (16.3.4902.3112)\u003c/li\u003e\u003c/ul\u003ePatch planned in:\u003cbr\u003e\u003cul\u003e\u003cli\u003ePcVue 15.2.14\u003c/li\u003e\u003c/ul\u003e"
            }
          ],
          "value": "Harden the configuration\nWho should apply this recommendation: All users\n\n\nTo reduce the risk of exploitation, ARC Informatique strongly recommends implementing the following defensive measures:\n\n  *  Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from insecure networks.\n  *  Locate control system networks and remote devices behind firewalls and isolate them from business networks.\n  *  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.\n\n\n\nUninstall the Web Server \nWho should apply this recommendation: All users not using the affected component \n\nIf your system does not require the use of the Web \u0026 Mobile features, you should make sure not to install them. If your system requires the use of the Web \u0026 Mobile features, they should be installed only on the Web Server.\nSee the product help related to the installation for more information.\n\n\n\n\nUpdate IIS configuration \u2013 manually update HTTP headers\nWho should apply this recommendation: \n\nAll users running affected components.\n\n\n\nAs a quick mitigation for the unnecessary and missing HTTP headers, you can disable default headers and add secure HTTP headers for all requests. Those options can be set via the web.config file located on the IIS by following those steps:\n  *  Open the file C:\\inetpub\\\u003cSV Website\u003e\\web.config\n  *  Add the following entries to the section customHeaders, which are the recommendations from the official OWASP site:\n\u003cremove name=\"X-Powered-By\" /\u003e\n\u003cadd name=\"X-Frame-Options\" value=\"DENY\" /\u003e\n\u003cadd name=\"X-XSS-Protection\" value=\"0\" /\u003e\n\u003cadd name=\"X-Content-Type-Options\" value=\"nosniff\" /\u003e\n\u003cadd name=\"X-DNS-Prefetch-Control\" value=\"off\" /\u003e\n\u003cadd name=\"Cross-Origin-Opener-Policy\" value=\"same-origin\" /\u003e\n\u003cadd name=\"Cross-Origin-Embedder-Policy\" value=\"require-corp\" /\u003e\n\u003cadd name=\"Cross-Origin-Resource-Policy\" value=\"same-site\" /\u003e\n\u003cadd name=\"Referrer-Policy\" value=\"strict-origin-when-cross-origin\" /\u003e\n\u003cadd name=\"Strict-Transport-Security\" value=\"max-age=63072000; includeSubDomains; preload\" /\u003e\n\u003cadd name=\"Permissions-Policy\" value=\"geolocation=(), camera=(), microphone=()\" /\u003e\n\n\nUpdate the Web Deployment Console (WDC) and re deploy the Web Server\nWho should apply this recommendation: \n\nAll users running affected components.\n\n\n\nInstall 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.\n\nIn a patched release of the WDC, new settings are available for each authorized Client to enable or disable:\n  *  The Authorization Code flow\n  *  The Authorization Code flow with PKCE\n  *  The Resource Owner Password Credentials (ROPC) flow\n\n\nBy default, all the OAuth flows are now disabled for third-party web apps and need to be manually enabled before deployment if required.\n\nTo verify that the patch is applied correctly, you must check that:\n  *  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;\n  *  Web Sites have been redeployed;\n  *  OAuth flow are correctly set for each authorized Client.\n\n\n\n\n\n\n\nAvailable patches:\nPatch provided in:\n  *  PcVue 16.3.4 (16.3.4902.3112)\n\n\nPatch planned in:\n  *  PcVue 15.2.14"
        }
      ],
      "source": {
        "advisory": "SB2026-2",
        "discovery": "EXTERNAL"
      },
      "title": "Server configuration details in HTTP headers",
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932",
    "assignerShortName": "arcinfo",
    "cveId": "CVE-2026-1694",
    "datePublished": "2026-02-26T07:56:57.048Z",
    "dateReserved": "2026-01-30T08:37:56.659Z",
    "dateUpdated": "2026-02-26T14:22:11.880Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-1694\",\"sourceIdentifier\":\"87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932\",\"published\":\"2026-02-26T08:16:18.763\",\"lastModified\":\"2026-02-27T14:06:59.787\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.\"}],\"metrics\":{\"cvssMetricV40\":[{\"source\":\"87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"4.0\",\"vectorString\":\"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:X/RE:M/U:Clear\",\"baseScore\":2.3,\"baseSeverity\":\"LOW\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"attackRequirements\":\"NONE\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"PASSIVE\",\"vulnConfidentialityImpact\":\"NONE\",\"vulnIntegrityImpact\":\"NONE\",\"vulnAvailabilityImpact\":\"NONE\",\"subConfidentialityImpact\":\"LOW\",\"subIntegrityImpact\":\"NONE\",\"subAvailabilityImpact\":\"NONE\",\"exploitMaturity\":\"NOT_DEFINED\",\"confidentialityRequirement\":\"NOT_DEFINED\",\"integrityRequirement\":\"NOT_DEFINED\",\"availabilityRequirement\":\"NOT_DEFINED\",\"modifiedAttackVector\":\"NOT_DEFINED\",\"modifiedAttackComplexity\":\"NOT_DEFINED\",\"modifiedAttackRequirements\":\"NOT_DEFINED\",\"modifiedPrivilegesRequired\":\"NOT_DEFINED\",\"modifiedUserInteraction\":\"NOT_DEFINED\",\"modifiedVulnConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedVulnIntegrityImpact\":\"NOT_DEFINED\",\"modifiedVulnAvailabilityImpact\":\"NOT_DEFINED\",\"modifiedSubConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedSubIntegrityImpact\":\"NOT_DEFINED\",\"modifiedSubAvailabilityImpact\":\"NOT_DEFINED\",\"Safety\":\"NOT_DEFINED\",\"Automatable\":\"YES\",\"Recovery\":\"USER\",\"valueDensity\":\"NOT_DEFINED\",\"vulnerabilityResponseEffort\":\"MODERATE\",\"providerUrgency\":\"CLEAR\"}}]},\"weaknesses\":[{\"source\":\"87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-201\"}]}],\"references\":[{\"url\":\"https://www.pcvue.com/security/#SB2026-2\",\"source\":\"87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-1694\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-02-26T14:22:01.724842Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-02-26T14:22:07.242Z\"}}], \"cna\": {\"title\": \"Server configuration details in HTTP headers\", \"source\": {\"advisory\": \"SB2026-2\", \"discovery\": \"EXTERNAL\"}, \"metrics\": [{\"format\": \"CVSS\", \"cvssV4_0\": {\"Safety\": \"NOT_DEFINED\", \"version\": \"4.0\", \"Recovery\": \"USER\", \"baseScore\": 2.3, \"Automatable\": \"YES\", \"attackVector\": \"NETWORK\", \"baseSeverity\": \"LOW\", \"valueDensity\": \"NOT_DEFINED\", \"vectorString\": \"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:U/RE:M/U:Clear\", \"exploitMaturity\": \"NOT_DEFINED\", \"providerUrgency\": \"CLEAR\", \"userInteraction\": \"PASSIVE\", \"attackComplexity\": \"HIGH\", \"attackRequirements\": \"NONE\", \"privilegesRequired\": \"NONE\", \"subIntegrityImpact\": \"NONE\", \"vulnIntegrityImpact\": \"NONE\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"NONE\", \"subConfidentialityImpact\": \"LOW\", \"vulnConfidentialityImpact\": \"NONE\", \"vulnerabilityResponseEffort\": \"MODERATE\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"role\": \"CNA\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\"}}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"arcinfo\", \"modules\": [\"WebVue\", \"WebScheduler\", \"TouchVue\", \"SnapVue\", \"Web services\"], \"product\": \"PcVue\", \"versions\": [{\"status\": \"affected\", \"version\": \"16.0.0\", \"versionType\": \"cpe\", \"lessThanOrEqual\": \"16.3.3\"}, {\"status\": \"affected\", \"version\": \"15.0.0\", \"versionType\": \"cpe\", \"lessThanOrEqual\": \"15.2.13\"}, {\"status\": \"affected\", \"version\": \"12.0.0\", \"versionType\": \"cpe\"}], \"defaultStatus\": \"unaffected\"}], \"exploits\": [{\"lang\": \"en\", \"value\": \"No POC available.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"No POC available.\", \"base64\": false}]}, {\"lang\": \"en\", \"value\": \"Not known to be exploited\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Not known to be exploited\", \"base64\": false}]}], \"solutions\": [{\"lang\": \"en\", \"value\": \"Harden the configuration\\nWho should apply this recommendation: All users\\n\\n\\nTo reduce the risk of exploitation, ARC Informatique strongly recommends implementing the following defensive measures:\\n\\n  *  Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from insecure networks.\\n  *  Locate control system networks and remote devices behind firewalls and isolate them from business networks.\\n  *  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.\\n\\n\\n\\nUninstall the Web Server \\nWho should apply this recommendation: All users not using the affected component \\n\\nIf your system does not require the use of the Web \u0026 Mobile features, you should make sure not to install them. If your system requires the use of the Web \u0026 Mobile features, they should be installed only on the Web Server.\\nSee the product help related to the installation for more information.\\n\\n\\n\\n\\nUpdate IIS configuration \\u2013 manually update HTTP headers\\nWho should apply this recommendation: \\n\\nAll users running affected components.\\n\\n\\n\\nAs a quick mitigation for the unnecessary and missing HTTP headers, you can disable default headers and add secure HTTP headers for all requests. Those options can be set via the web.config file located on the IIS by following those steps:\\n  *  Open the file C:\\\\inetpub\\\\\u003cSV Website\u003e\\\\web.config\\n  *  Add the following entries to the section customHeaders, which are the recommendations from the official OWASP site:\\n\u003cremove name=\\\"X-Powered-By\\\" /\u003e\\n\u003cadd name=\\\"X-Frame-Options\\\" value=\\\"DENY\\\" /\u003e\\n\u003cadd name=\\\"X-XSS-Protection\\\" value=\\\"0\\\" /\u003e\\n\u003cadd name=\\\"X-Content-Type-Options\\\" value=\\\"nosniff\\\" /\u003e\\n\u003cadd name=\\\"X-DNS-Prefetch-Control\\\" value=\\\"off\\\" /\u003e\\n\u003cadd name=\\\"Cross-Origin-Opener-Policy\\\" value=\\\"same-origin\\\" /\u003e\\n\u003cadd name=\\\"Cross-Origin-Embedder-Policy\\\" value=\\\"require-corp\\\" /\u003e\\n\u003cadd name=\\\"Cross-Origin-Resource-Policy\\\" value=\\\"same-site\\\" /\u003e\\n\u003cadd name=\\\"Referrer-Policy\\\" value=\\\"strict-origin-when-cross-origin\\\" /\u003e\\n\u003cadd name=\\\"Strict-Transport-Security\\\" value=\\\"max-age=63072000; includeSubDomains; preload\\\" /\u003e\\n\u003cadd name=\\\"Permissions-Policy\\\" value=\\\"geolocation=(), camera=(), microphone=()\\\" /\u003e\\n\\n\\nUpdate the Web Deployment Console (WDC) and re deploy the Web Server\\nWho should apply this recommendation: \\n\\nAll users running affected components.\\n\\n\\n\\nInstall 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.\\n\\nIn a patched release of the WDC, new settings are available for each authorized Client to enable or disable:\\n  *  The Authorization Code flow\\n  *  The Authorization Code flow with PKCE\\n  *  The Resource Owner Password Credentials (ROPC) flow\\n\\n\\nBy default, all the OAuth flows are now disabled for third-party web apps and need to be manually enabled before deployment if required.\\n\\nTo verify that the patch is applied correctly, you must check that:\\n  *  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;\\n  *  Web Sites have been redeployed;\\n  *  OAuth flow are correctly set for each authorized Client.\\n\\n\\n\\n\\n\\n\\n\\nAvailable patches:\\nPatch provided in:\\n  *  PcVue 16.3.4 (16.3.4902.3112)\\n\\n\\nPatch planned in:\\n  *  PcVue 15.2.14\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cb\u003e\u003c/b\u003e\\n\\n\u003cb\u003eHarden the configuration\u003c/b\u003e\u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e All users\u003cbr\u003e\\n\\nTo reduce the risk of exploitation, ARC Informatique strongly recommends implementing the following defensive measures:\\n\\n\u003cul\u003e\u003cli\u003eMinimize network exposure for all control system devices and/or systems, and ensure they are not accessible from insecure networks.\u003c/li\u003e\u003cli\u003eLocate control system networks and remote devices behind firewalls and isolate them from business networks.\u003c/li\u003e\u003cli\u003eWhen 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.\u003c/li\u003e\u003c/ul\u003e\u003cbr\u003e\u003cb\u003eUninstall the Web Server\u003c/b\u003e \u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e All users \u003cb\u003enot \u003c/b\u003eusing the affected component \u003cbr\u003e\u003cbr\u003eIf your system does not require the use of the Web \u0026amp; Mobile features, you should make sure not to install them. If your system requires the use of the Web \u0026amp; Mobile features, they should be installed only on the Web Server.\u003cbr\u003eSee the product help related to the installation for more information.\\n\\n\u003cbr\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eUpdate IIS configuration \\u2013 manually update HTTP headers\u003c/b\u003e\u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e \\n\\nAll users running affected components.\\n\\n\u003cbr\u003e\u003cbr\u003eAs a quick mitigation for the unnecessary and missing HTTP headers, you can disable default headers and add secure HTTP headers for all requests. Those options can be set via the web.config file located on the IIS by following those steps:\u003cbr\u003e\u003col\u003e\u003cli\u003eOpen the file \u003ci\u003eC:\\\\inetpub\\\\\u0026lt;SV Website\u0026gt;\\\\web.config\u003c/i\u003e\u003c/li\u003e\u003cli\u003eAdd the following entries to the section \u003ci\u003ecustomHeaders\u003c/i\u003e, which are the recommendations from the official OWASP site:\u003cbr\u003e\u0026lt;remove name=\\\"X-Powered-By\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"X-Frame-Options\\\" value=\\\"DENY\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"X-XSS-Protection\\\" value=\\\"0\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"X-Content-Type-Options\\\" value=\\\"nosniff\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"X-DNS-Prefetch-Control\\\" value=\\\"off\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"Cross-Origin-Opener-Policy\\\" value=\\\"same-origin\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"Cross-Origin-Embedder-Policy\\\" value=\\\"require-corp\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"Cross-Origin-Resource-Policy\\\" value=\\\"same-site\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"Referrer-Policy\\\" value=\\\"strict-origin-when-cross-origin\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"Strict-Transport-Security\\\" value=\\\"max-age=63072000; includeSubDomains; preload\\\" /\u0026gt;\u003cbr\u003e\u0026lt;add name=\\\"Permissions-Policy\\\" value=\\\"geolocation=(), camera=(), microphone=()\\\" /\u0026gt;\u003c/li\u003e\u003c/ol\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eUpdate the Web Deployment Console (WDC) and re deploy the Web Server\u003c/b\u003e\u003cbr\u003e\u003cu\u003eWho should apply this recommendation:\u003c/u\u003e \\n\\nAll users running affected components.\\n\\n\u003cbr\u003e\u003cbr\u003eInstall 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.\u003cbr\u003e\u003cbr\u003eIn a patched release of the WDC, new settings are available for each authorized Client to enable or disable:\u003cbr\u003e\u003cul\u003e\u003cli\u003eThe Authorization Code flow\u003c/li\u003e\u003cli\u003eThe Authorization Code flow with PKCE\u003c/li\u003e\u003cli\u003eThe Resource Owner Password Credentials (ROPC) flow\u003c/li\u003e\u003c/ul\u003eBy default, all the OAuth flows are now disabled for third-party web apps and need to be manually enabled before deployment if required.\u003cbr\u003e\u003cbr\u003eTo verify that the patch is applied correctly, you must check that:\u003cbr\u003e\u003cul\u003e\u003cli\u003eThe \u003ci\u003eFile version\u003c/i\u003e property of the file \u003ci\u003e./bin/Modules/WebDeployment/WebDeploymentConsole.exe\u003c/i\u003e matches the deployed release or later, and ensure that any earlier release is no longer used;\u003c/li\u003e\u003cli\u003eWeb Sites have been redeployed;\u003c/li\u003e\u003cli\u003eOAuth flow are correctly set for each authorized Client.\u003c/li\u003e\u003c/ul\u003e\u003cbr\u003e\\n\\n\u003cb\u003e\u003c/b\u003e\\n\\n\u003cb\u003eAvailable patches:\u003c/b\u003e\u003cbr\u003ePatch provided in:\u003cbr\u003e\u003cul\u003e\u003cli\u003ePcVue 16.3.4 (16.3.4902.3112)\u003c/li\u003e\u003c/ul\u003ePatch planned in:\u003cbr\u003e\u003cul\u003e\u003cli\u003ePcVue 15.2.14\u003c/li\u003e\u003c/ul\u003e\", \"base64\": false}]}], \"datePublic\": \"2026-02-25T23:00:00.000Z\", \"references\": [{\"url\": \"https://www.pcvue.com/security/#SB2026-2\", \"tags\": [\"vendor-advisory\"]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.\u003cbr\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-201\", \"description\": \"CWE-201 Insertion of Sensitive Information into Sent Data\"}]}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:a:arcinfo:pcvue:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndIncluding\": \"16.3.3\", \"versionStartIncluding\": \"16.0.0\"}, {\"criteria\": \"cpe:2.3:a:arcinfo:pcvue:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndIncluding\": \"15.2.13\", \"versionStartIncluding\": \"15.0.0\"}, {\"criteria\": \"cpe:2.3:a:arcinfo:pcvue:12.0.0:*:*:*:*:*:*:*\", \"vulnerable\": true}], \"operator\": \"OR\"}], \"operator\": \"OR\"}], \"providerMetadata\": {\"orgId\": \"87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932\", \"shortName\": \"arcinfo\", \"dateUpdated\": \"2026-02-26T07:56:57.048Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-1694\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-02-26T14:22:11.880Z\", \"dateReserved\": \"2026-01-30T08:37:56.659Z\", \"assignerOrgId\": \"87c8e6ad-f0f5-4ca8-89e2-89f26d6ed932\", \"datePublished\": \"2026-02-26T07:56:57.048Z\", \"assignerShortName\": \"arcinfo\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.