CVE-2025-2919
Netis-Systems Netis Wf-2404 Firmware 1.1.124en
Raw vector
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:XSummary
CVE-2025-2919 is a high-severity Active Debug Code (CWE-489) vulnerability in Netis-Systems Netis Wf-2404 Firmware. Its CVSS base score is 7.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th 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-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-8634
Vulnerability Data
A vulnerability was found in Netis WF-2404 1.1.124EN. It has been declared as critical. This vulnerability affects unknown code of the component UART. The manipulation leads to hardware allows activation of test or debug logic at runtime. It is possible…
more
to launch the attack on the physical device. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Baseline configuration defines the approved production state that must exclude active debug code.
Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.
Documented development standards and tools can require removal of debug code before release.
Anti-tamper requirements on developers stop hardware debug features from being activatable at runtime.
Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.
Hardware-enforced write protection and procedures directly block unauthorized runtime activation of debug or test logic.
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.
Pre-acquisition hardware integrity assessment directly prevents introduction of devices with exposed debug logic.
Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.
Supplier-product risk assessment can identify and respond to hardware debug-feature exposure risks.
Hardware replacement policy can remove affected devices after discovery but does not prevent the weakness itself.
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.
Security testing in development and acceptance catches active debug code before deployment.
Configuration management can disable or remove debug features through hardened baselines.
Secure development life cycle mandates removal of debug code before release.
Secure system architecture and engineering principles require disabling or locking debug/test logic in production hardware.
Secure coding standards explicitly prohibit leaving debug code active in production.
Separation of environments reduces risk of debug code reaching production but does not directly address its removal.