Skip to content
Fencer Intel
critical 10.0

CVE-2014-9195 in the critical feed json

Phoenix Contact Software ProConOs and MultiProg Missing Authentication for Critical Function

published 2015-01-17 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9020

cvss
10.0
version 2.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
81.1%
EPSS 81.1% chance of exploitation in 30 days, percentile 99.6%
public exploits
2
Metasploit, Exploit-DB

Summary

Phoenix Contact ProConOs and MultiProg do not require authentication, which allows remote attackers to execute arbitrary commands via protocol-compliant traffic.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-26-279-06 updated cvss 8.1

Hitachi Energy RTU500

  • Hitachi Energy RTU500 series CMU Firmware vers:RTU500_series_CMU_Firmware/<=11.x
    affected: fixed in 12.7.8

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

cisa ICSA-15-013-03 updated cvss 10.0

Phoenix Contact Software ProConOs and MultiProg Authentication Vulnerability

  • Phoenix Contact Software MultiProg Phoenix Contact Software ProConOs
    affected: mitigation

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. Published
  2. First public exploit (Metasploit auxiliary/admin/scada/phoenix_command)

Exploit prediction

81.11% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Phoenix Contact ProConOs
  • Phoenix Contact MultiProg

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality
  • CWE-255 Credentials Management Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.