Remote device takeover via shared default credentials
Published Nov 19, 2025 · Updated Nov 19, 2025
Default credentials in Vivotek legacy device firmware allow remote attackers to access root and user accounts over the network. The firmware hard-codes the shared password mpeg4soc for both login identities instead of requiring a device-specific secret. Remote attackers need only network reachability; the shared root login grants full administrative control of the device.
Summary
What happened
Default credentials in Vivotek legacy device firmware allow remote attackers to access root and user accounts over the network. The firmware hard-codes the shared password mpeg4soc for both login identities instead of requiring a device-specific secret. Remote attackers need only network reachability; the shared root login grants full administrative control of the device.
The record
- CVE
- CVE-2025-12592
- Published
- Nov 19, 2025
- Updated
- Nov 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1392, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2025CVE publishedPublication date reported by the CVE source.
- Nov 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Published mpeg4soc default credentialfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo