CVE-2023-41960
Boschrexroth Ctrlx Hmi Web Panel Wr2107 Firmware
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41960 is a high-severity Improper Export of Android Application Components (CWE-926) vulnerability in Boschrexroth Ctrlx Hmi Web Panel Wr2107 Firmware. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 8th 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
- 🇪🇺 ENISA EUVD: EUVD-2023-46419
Vulnerability Data
The vulnerability allows an unprivileged(untrusted) third-party application to interact with a content-provider unsafely exposed by the Android Agent application, potentially modifying sensitive settings of the Android Client application itself.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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.
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.26 only requires that security requirements (including access segregation) be identified and specified during development; it does not itself enforce, implement or configure the restrictions that would stop an improperly-exported Android component from being launched or accessed by unauthorized apps.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust external input, zero-trust verification) and design reviews that can stop unsafe component export decisions, but this is only one slice of the weakness class; many export flaws arise from concrete permission/Intent-filter misconfigurations that the high-level principles and reviews do not themselves enforce.
Secure-coding standards require explicit permission declarations and intent-filter restrictions to avoid improper exports.
Security testing can detect exported components lacking proper restrictions, providing partial coverage of the weakness.
Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.