PatchTheCVEgovicture vulnerabilities
Recent CVEs affecting govicture products. 7 tracked.
govicture has 7 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-05-09. Highest priority: CVE-2025-28200 (score 57/100).
- CVE-2025-28200 CRITICAL 9.8 MITIGATE Victure RX1800 EN_V1.0.0_r12_110933 was discovered to utilize a weak default password which includes the last
- CVE-2025-28203 HIGH 8.8 MITIGATE Victure RX1800 EN_V1.0.0_r12_110933 was discovered to contain a command injection vulnerability.
- CVE-2025-28202 HIGH 8.8 MITIGATE Incorrect access control in Victure RX1800 EN_V1.0.0_r12_110933 allows attackers to enable SSH and Telnet serv
- CVE-2025-28201 MEDIUM 6.8 MITIGATE An issue in Victure RX1800 EN_V1.0.0_r12_110933 allows physically proximate attackers to execute arbitrary cod
- CVE-2023-41612 HIGH 8.8 MITIGATE Victure PC420 1.1.39 was discovered to use a weak encryption key for the file enabled_telnet.dat on the Micro
- CVE-2023-41611 MEDIUM 6.5 MITIGATE Victure PC420 1.1.39 was discovered to use a weak and partially hardcoded key to encrypt data.
- CVE-2023-41610 HIGH 8.8 MITIGATE Victure PC420 1.1.39 was discovered to contain a hardcoded root password which is stored in plaintext.
FAQ
How do I fix govicture vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is govicture being exploited right now?
None of the tracked govicture CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which govicture CVE should I patch first?
CVE-2025-28200 currently ranks highest (57/100): Victure RX1800 EN_V1.0.0_r12_110933 was discovered to utilize a weak default password which includes the last .