Cyber Resilience

CVE-2025-34081

Info Disclosure in Contec Conprosys Hmi System ≤ 3.7.7

Public PoCInfo Disclosure
Published
01 July 2025
Modified
17 June 2026
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/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:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0060 46th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2025-34081 is a medium-severity Insertion of Sensitive Information Into Debugging Code (CWE-215) vulnerability in Contec Conprosys Hmi System. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to CM-7 (Least Functionality) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-215

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-28713Same product: Contec Conprosys Hmi System
CVE-2023-28399Same product: Contec Conprosys Hmi System
CVE-2023-22331Same product: Contec Conprosys Hmi System
CVE-2022-44456Same product: Contec Conprosys Hmi System
CVE-2023-22334Same product: Contec Conprosys Hmi System
CVE-2023-22373Same product: Contec Conprosys Hmi System
CVE-2023-28657Same product: Contec Conprosys Hmi System
CVE-2023-2758Same product: Contec Conprosys Hmi System
CVE-2023-22324Same product: Contec Conprosys Hmi System
CVE-2023-28651Same product: Contec Conprosys Hmi System

Affected Assets

contec
conprosys hmi system
≤ 3.7.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V13.4.2

Mitigating Controls (NIST 800-53 r5) AI

CM-7 Least Functionality good match

Least functionality directly prohibits enabling unnecessary debug features that would expose the inserted sensitive data.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation will discover debug code containing sensitive information before release.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure development processes and standards stops insertion of sensitive data into debug paths.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent developers from embedding sensitive information inside debugging statements or code paths.

PR.DS-10 partial match
prevents

Explicitly calls for removing confidential data from processes, logs, and memory dumps that debug code commonly exposes.

PR.PS-01 partial match
prevents

Hardened configuration baselines and deployment checks can ensure debug features and associated data are disabled in production.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches debug statements and sensitive data leaks.

A.8.31 Separation of development, test and production environments mostly match
prevents

Separation of environments reduces accidental exposure of debug builds to production.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates removal of debug code and sensitive data before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit embedding secrets or debug statements.

A.8.15 Logging none match
none

Logging controls may capture debug output, but do not prevent its creation.

A.8.33 Test information none match
none

Test data handling rules discourage use of real sensitive data in debug contexts.

References