Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-65552 is a critical-severity Authentication Bypass by Capture-replay (CWE-294) vulnerability in D3Dsecurity Zx-G12 Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 29th 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 SC-23 (Session Authenticity) and SC-8 (Transmission Confidentiality and Integrity) — 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-65552 affects the D3D Wi-Fi Home Security System ZX-G12 running firmware version v2.1.1. The vulnerability involves RF replay attacks on the 433 MHz sensor communication channel, as the system lacks rolling codes, message authentication, or anti-replay protection. This allows an attacker to record valid alarm or control frames and replay them, leading to false alarms. The issue is classified under CWE-294 and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), published on 2026-01-12.
An attacker within RF range of the targeted system can exploit this vulnerability without authentication or user interaction. By capturing legitimate frames transmitted over the 433 MHz channel using readily available software-defined radio tools, the attacker can replay them to manipulate the security system, such as triggering unauthorized alarms or control actions.
Further details, including potential proof-of-concept code, are available in the listed references: the vendor site at http://d3d.com and product page at https://d3dsecurity.com/products/wifi-home-security-system-model-g12, as well as the GitHub repository at https://github.com/EmbdCDACHyd/CVE/tree/main/CVE-2025-65552. No specific mitigation or patch information is detailed in the provided CVE data.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1934
Vulnerability Data
D3D Wi-Fi Home Security System ZX-G12 v2.1.1 is vulnerable to RF replay attacks on the 433 MHz sensor communication channel. The system does not implement rolling codes, message authentication, or anti-replay protection, allowing an attacker within RF range to record…
more
valid alarm/control frames and replay them to trigger false alarms.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.4.16V10.5.1
Mitigating Controls (NIST 800-53 r5) AI
Session authenticity mechanisms directly stop replay of captured authentication traffic by enforcing freshness or cryptographic binding.
Transmission integrity (with anti-replay) stops captured messages from being accepted as valid later.
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.
Protecting and verifying identity assertions prevents replay of captured authentication material.
Encryption and integrity protections for data-in-transit directly block capture-replay of credentials or tokens.
Network monitoring may detect anomalous replays after the fact but does not prevent the design flaw.
Strong authentication methods can reduce replay risk but do not inherently address captured messages.
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.
Cryptographic protections (e.g., nonces, timestamps, message authentication codes) make captured authentication messages unusable for replay.
Secure authentication mechanisms directly prevent replay attacks by requiring fresh, non-replayable credentials or tokens.
Network security controls such as encryption and integrity protection reduce the feasibility of capturing and replaying authentication traffic.
Application security requirements can mandate replay-resistant authentication designs, but the control itself does not prescribe the technical measures.