Security Resilience

CVE-2023-4487

Ge Cimplicity 2023

Published
05 September 2023
Modified
21 November 2024
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0020 10th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-4487 is a high-severity Process Control (CWE-114) vulnerability in Ge Cimplicity. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

GE CIMPLICITY 2023 is by a process control vulnerability, which could allow a local attacker to insert malicious configuration files in the expected web server execution path to escalate privileges and gain full control of the HMI software.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-3463Same product: Ge Cimplicity
CVE-2023-0598Same vendor: Ge
CVE-2023-1552Same vendor: Ge
CVE-2023-0898Same vendor: Ge
CVE-2024-32004Shared CWE-114
CVE-2026-92939Shared CWE-114
CVE-2025-36250Shared CWE-114
CVE-2025-23385Shared CWE-114
CVE-2026-26945Shared CWE-114
CVE-2023-40299Shared CWE-114

Affected Assets

ge
cimplicity
2023

Mitigating Controls

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.

blocks

A.8.19's rules on approved code only, testing before install, least-privilege installation rights, and avoiding untrusted external packages directly stop many untrusted-source process-control cases from being introduced or exploited on operational systems, but leave a bounded remainder (e.g. untrusted libraries already present at build time, runtime dynamic loading decisions outside the install boundary, or flaws in the approved code itself).

degrades

Secure development lifecycle practices include controls on external code and command execution paths.

blocks

Application security requirements can mandate validation of external inputs and libraries.

blocks

A.8.27 mandates security-by-design principles (least privilege, distrust external input, fail securely, defence-in-depth, hardening, zero-trust verification) that reach some but not most instances of CWE-114; a bounded remainder (e.g. unsafe library loading in custom code or third-party components where principles are applied incompletely) is left.

prevents

Secure coding standards explicitly forbid executing or loading code from untrusted sources.

finds

Security testing can detect unsafe process or library loading but does not prevent it by itself.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-114, a class-level weakness, and none of its children carries one either.

References