CVE-2025-25983
Macro-Video V380 Pro 2.1.44 … 2.1.64
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:N/A:NSummary
CVE-2025-25983 is a low-severity Storing Passwords in a Recoverable Format (CWE-257) vulnerability in Macro-Video V380 Pro. Its CVSS base score is 3.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Group Policy Preferences (T1552.006); ranked at the 22th 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 IA-5 (Authenticator Management) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-11895
Vulnerability Data
An issue in Macro-video Technologies Co.,Ltd V380 Pro android application 2.1.44 and V380 Pro android application 2.1.64 allows an attacker to obtain sensitive information via the QE code based sharing component.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V11.4.2V11.4.4V6.3.4
Mitigating Controls (NIST 800-53 r5) AI
IA-5 requires proper management of authenticators including storage of passwords only in non-recoverable (hashed) form, directly stopping the weakness from existing.
Requires selection and implementation of approved cryptographic methods whose strength does not rest on secrecy of design.
Security and privacy engineering principles explicitly prohibit reliance on obscurity and require documented, verifiable protection mechanisms.
Requires cryptographic or equivalent protection of information at rest, eliminating dependence on obscurity for confidentiality.
Mandates actual cryptographic or equivalent protection of transmitted data rather than depending on hidden algorithms or keys.
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 data-at-rest with cryptographic hashes directly prevents recoverable password storage.
Secure SDLC practices explicitly reject obscurity-based designs in favor of proven controls.
Risk-management policy can mandate avoidance of obscurity but does not itself implement technical alternatives.
Risk analysis surfaces obscurity as a weakness yet does not prevent its introduction.
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.
Directly requires secure handling and protection of authentication information, preventing storage in recoverable formats.
Mandates secure authentication mechanisms that preclude recoverable password storage.
Mandates use of cryptography whose strength is independent of secrecy of design or keys.
Requires secure architecture and engineering principles that reject reliance on obscurity.
Secure SDLC includes requirements that reduce the likelihood of introducing recoverable password storage.
Secure coding practices can prevent developers from implementing recoverable password storage.