Anviz vulnerabilities
We track 7 vulnerabilities in Anviz products across 6 products. 7 are rated high or critical, and none are known to be exploited. The most recent was published on April 17, 2026.
Latest Anviz vulnerabilities
- 7.5 High severity
Anviz CX7 Firmware: Missing Authentication for Critical Functionality
Anviz CX2 Lite and CX7 are vulnerable to unauthenticated POST requests that modify debug settings (e.g., enabling SSH), allowing unauthorized state changes that can facilitate later compromise.
- 8.1 High severity
Anviz CrossChex Standard: Improper Verification of Source of a Communication Channel
Anviz CrossChex Standard lacks source verification in the client/server channel, enabling TCP packet injection by an attacker on the same network to alter or disrupt application traffic.
- 8.8 High severity
Anviz CX7 Firmware: Download of Code Without Integrity Check
Anviz CX2 Lite and CX7 are vulnerable to unverified update packages that can be uploaded. The device unpacks and executes a script resulting in unauthenticated remote code execution.
- 8.8 High severity
Anviz CX2 Lite Firmware: Improper Neutralization of Special Elements used in a Command
Anviz CX2 Lite is vulnerable to an authenticated command injection via a filename parameter that enables arbitrary command execution (e.g., starting telnetd), resulting in root‑level access.
- 9.8 Critical severity
Anviz CX7 Firmware: Missing Authentication for Critical Functionality
Anviz CX2 Lite and CX7 are vulnerable to unauthenticated firmware uploads. This causes crafted archives to be accepted, enabling attackers to plant and execute code and obtain a reverse shell.
- 7.5 High severity
Anviz CrossChex Standard: Selection of Less-Secure Algorithm During Negotiation
Anviz CrossChex Standard is vulnerable when an attacker manipulates the TDS7 PreLogin to disable encryption, causing database credentials to be sent in plaintext and enabling unauthorized database access.
- 7.7 High severity
Anviz CX7 Firmware: Use of Hard-coded Cryptographic Key
Anviz CX7 Firmware is vulnerable because the application embeds reusable certificate/key material, enabling decryption of MQTT traffic and potential interaction with device messaging channels at scale.