Cyber Resilience

CVE-2025-0675

Published
07 February 2025
Modified
15 April 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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.0050 41th percentile
Risk Priority 45 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-2025-0675 is a high-severity Hidden Functionality (CWE-912) vulnerability in Cisa (inferred from references). Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-0675 is an information disclosure vulnerability affecting multiple Elber products, enabling unauthenticated access to device configuration data and client-side hidden functionality. Published on 2025-02-07, it carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and is linked to CWE-912 (Hidden Functionality).

Remote attackers require only network access and face low complexity barriers, with no privileges, authentication, or user interaction needed. Successful exploitation allows disclosure of sensitive configuration details and hidden features, resulting in high confidentiality impact without affecting integrity or availability.

The CISA ICS Advisory ICSA-25-035-03 provides details on mitigation strategies and affected products; practitioners should consult https://www.cisa.gov/news-events/ics-advisories/icsa-25-035-03 for patches and remediation guidance.

EU & UK References

Vulnerability Data

Multiple Elber products suffer from an unauthenticated device configuration and client-side hidden functionality disclosure.

CWE(s)
CWE-912

Related Threats

MITRE ATT&CK Enterprise Techniques

T1108 Redundant Access Stealth
**This technique has been deprecated.
attack.mitre.org →
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
attack.mitre.org →
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
attack.mitre.org →
T1554 Compromise Host Software Binary Persistence
Adversaries may modify host software binaries to establish persistent access to systems.
attack.mitre.org →
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-37990Shared CWE-912
CVE-2025-55075Shared CWE-912
CVE-2026-33280Shared CWE-912
CVE-2025-9382Shared CWE-912
CVE-2023-42134Shared CWE-912
CVE-2026-30704Shared CWE-912
CVE-2026-61515Shared CWE-912
CVE-2025-46267Shared CWE-912
CVE-2025-58778Shared CWE-912
CVE-2025-11673Shared CWE-912

Affected Assets

Cisa
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

CM-2 Baseline Configuration good match

Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.

CM-7 Least Functionality good match

Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.

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

Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.

SA-3 System Development Life Cycle partial match

An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.

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 full match
prevents

Secure SDLC practices directly prevent introduction of undocumented hidden functionality during development.

ID.RA-09 mostly match
prevents

Pre-acquisition integrity/authenticity checks can detect undocumented hidden functions in supplied software/hardware.

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 and acceptance can discover undocumented functionality before release.

A.8.32 Change management mostly match
prevents

Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.

A.8.16 Monitoring activities partial match
finds

Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly define expected functionality, making hidden features a violation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.

References