VulnerabilityPublished 1 Jul 2025Updated 21 Nov 2025

CVE-2025-34081: Contec CONPROSYS HMI System (CHS) · Insertion of Sensitive Information Into Debugging Code

Affects Contec CONPROSYS HMI System (CHS)Source CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Contec Co.,Ltd. CONPROSYS HMI System (CHS)	Affected =0	Fixed in–

AI-suggested

Immediate mitigation steps include restricting access to the phpinfo() debug page by implementing web server access controls such as IP whitelisting, authentication requirements, or disabling the debug page entirely in production environments. Network segmentation should be enforced to isolate HMI systems from general enterprise networks and the internet, limiting exposure to potential attackers. Monitoring and logging access to web interfaces can help detect unauthorized attempts to access debug pages. Organizations should contact Contec Co.,Ltd. for official patches or updates addressing this vulnerability and apply them promptly once available. Additionally, reviewing and hardening PHP configurations to disable unnecessary debug features and removing any development or debug code from production systems is recommended. Conducting regular security assessments and penetration testing on industrial control systems can help identify similar exposures. Finally, educating operational technology (OT) personnel about the risks of exposing debug information and enforcing secure development lifecycle practices will reduce future risks.

Description

The Contec Co.,Ltd. CONPROSYS HMI System (CHS) exposes a PHP phpinfo() debug page to unauthenticated users that may contain sensitive data useful for an attacker.This issue affects CONPROSYS HMI System (CHS): before 3.7.7.

Impact

For European organizations, especially those in industrial automation, manufacturing, and critical infrastructure sectors using CONPROSYS HMI System, this vulnerability poses a risk of sensitive information disclosure. Attackers gaining access to phpinfo() output can learn about server configurations, software versions, environment variables, and potentially sensitive credentials or paths. This information can facilitate more sophisticated attacks such as privilege escalation, remote code execution, or lateral movement within networks. While the vulnerability itself does not allow direct system compromise, it lowers the attacker's effort to identify weaknesses. European industries relying on automation and control systems are increasingly targeted by cyber threats, making such information disclosures particularly concerning. The exposure could also lead to compliance issues under regulations like GDPR if sensitive personal or operational data is indirectly exposed. The risk is heightened in environments where network segmentation and access controls are weak, allowing attackers to reach the vulnerable HMI systems from external or less trusted internal networks.

CWE-215Insertion of Sensitive Information Into Debugging Code (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
Implementation
Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 20:14 UTC

WeaknessesCWE-215

Technical details

References

Community reviews

Related threats