CVE-2020-5536: OpenBlocks IoT VX2 prior to Ver.4.0.0 (Ver.3 Series) allows an attacker on the same network segment to bypass

Q: How do I fix CVE-2020-5536?

openblocks iot vx2 firmware: upgrade to 4.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-5536 being exploited?

CVE-2020-5536 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-5536 affect?

CVE-2020-5536 affects openblocks iot vx2 firmware. Severity is high (CVSS 8.8). OpenBlocks IoT VX2 prior to Ver.4.0.0 (Ver.3 Series) allows an attacker on the same network segment to bypass authentication and to initialize the device via unspecified vectors.

This month

HIGH 8.8UPGRADE

CVE-2020-5536 is a high-severity flaw (CVSS 8.8) affecting openblocks iot vx2 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

OpenBlocks IoT VX2 prior to Ver.4.0.0 (Ver.3 Series) allows an attacker on the same network segment to bypass authentication and to initialize the device via unspecified vectors.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-287
Published	2020-03-04
Last modified	2026-06-17

Publisher (CNA): JPCERT/CC · Vendor: plathome

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-03-04 02:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

plathome openblocks iot vx2 firmware UPGRADE

Affected: >= 3.3.0 and < 4.0.0

Fixed in: 4.0.0

Safe to downgrade to: a release before 3.3.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5536?

openblocks iot vx2 firmware: upgrade to 4.0.0. Exact commands for each OS are on this page.

Is CVE-2020-5536 being exploited?

CVE-2020-5536 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5536 affect?

CVE-2020-5536 affects openblocks iot vx2 firmware. Severity is high (CVSS 8.8). OpenBlocks IoT VX2 prior to Ver.4.0.0 (Ver.3 Series) allows an attacker on the same network segment to bypass authentication and to initialize the device via unspecified vectors.

How urgent is CVE-2020-5536?

Priority 43/100. High severity

Related CVEs

CVE-2020-5535 HIGH 8.8 UPGRADE OpenBlocks IoT VX2 prior to Ver.4.0.0 (Ver.3 Series) allows an attacker on the same network segment to execute

References

← Back to latest CVEs