Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2025-9999

Improper validation of payload elements

High7.6EPSS 0.16%
Published
Updated
Reserved
Assigned by
arcinfo

Description

Some payload elements of the messages sent between two stations in a networking architecture are not properly checked on the receiving station allowing an attacker to execute unauthorized commands in the application.

Scores

CVSS scores of CVE-2025-9999, by who scored it
Scored byCVSSScoreVector
arcinfoCNA (assigner)4.0High7.6CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/AU:Y/R:U/RE:M/U:Green
NVDNVD · Deferred4.0High7.6CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/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:Green
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (5 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.6.

Weakness

Affected products

  • arcinfo · PcVue

    • affected 16.0.0 – ≤ 16.3.3
    • affected 15.0.0 – ≤ 15.2.12
    • affected 12.0.0 – ≤ 12.0.31

What to do

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 unsecure 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. Update PcVue Who should apply this recommendation: All users running affected components. Apply the patch by installing a fixed PcVue version. A fixed release must be installed on all stations for the fix to be fully applied. Existing projects require a settings update for the fix to be applied. The complete update procedure and verification steps are described in the Knowledge Base article KB1254 ( https://www.pcvue.com/?post_type=post&s=&kbase_id=kb1254 ) . For new projects, the settings are configured by default with secured values. To verify that the patch has been applied correctly, the user must check that: * The File version property of the file ./bin/sv32.exe matches the deployed release or later, and ensure that any earlier release is no longer used; * The Interoperability issues settings of the Networking feature are disabled. Available patches: Patch provided in: * PcVue 16.3.4 (16.3.4902.3112) * PcVue 15.2.13 (15.2.13902.37126) * PcVue 12.0.32 (12.0.32900.37130)

Exploitation: No POC available.

Exploitation: Not known to be exploited

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-9999 badge
[![CVE-2025-9999](https://trackcve.app/badge/CVE-2025-9999.svg)](https://trackcve.app/cve/CVE-2025-9999)

Record last updated .