Skip to main content
VulnerabilityPublished Updated

CVE-2026-1696: arcinfo PcVue · XSS or 'Cross-site Scripting'

Affects arcinfo PcVueSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
arcinfoPcVueAffected
  • >=16.0.0 <=16.3.3
  • >=15.0.0 <=15.2.13
  • =12.0.0
Fixed in–

AI-suggested

To mitigate CVE-2026-1696, organizations should implement the following specific measures: 1) Configure the web server hosting PcVue to set robust HTTP security headers, including Content-Security-Policy (CSP) to restrict script sources, X-Content-Type-Options to prevent MIME sniffing, X-Frame-Options to prevent clickjacking, and Referrer-Policy to control referrer information. 2) Employ input validation and output encoding within the PcVue application or any custom web interfaces to neutralize potentially malicious input before rendering. 3) Use web application firewalls (WAFs) with rules designed to detect and block XSS attack patterns targeting PcVue endpoints. 4) Educate users to recognize and avoid interacting with suspicious links or content that could trigger XSS payloads. 5) Monitor web server logs and application behavior for anomalous requests or script execution attempts. 6) Stay updated with arcinfo advisories for any forthcoming patches or updates addressing this vulnerability. 7) If feasible, isolate PcVue web interfaces within network segments with restricted access to reduce exposure. These targeted actions go beyond generic advice by focusing on header configuration, user awareness, and network segmentation specific to PcVue environments.

Description

Some HTTP security headers are not properly set by the web server when sending responses to the client application.

References

Community reviews

Loading reviews…