CVE-2020-35570

MEDIUMNVD 5.35.3—

5.3

An issue was discovered in MB connect line mymbCONNECT24, mbCONNECT24 and Helmholz myREX24 and myREX24.virtual through 2.11.2. An unauthenticated attacker is able to access files (that should have been restricted) via forceful browsing.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 74.3%
KEV: Not listed

Published

February 16, 2021

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://cert.vde.com/en/advisories/VDE-2021-003
cve@mitrehttps://cert.vde.com/en/advisories/VDE-2022-039
cve@mitrehttps://mbconnectline.com/security-advice/
af854a3a-2127-422b-91ae-364da2661108https://cert.vde.com/en/advisories/VDE-2021-003
af854a3a-2127-422b-91ae-364da2661108https://cert.vde.com/en/advisories/VDE-2022-039
af854a3a-2127-422b-91ae-364da2661108https://mbconnectline.com/security-advice/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-425

Data Freshness Timeline

(refreshed 10× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 20:46 UTCEG score recompute
2026-05-26 20:46 UTCGHSA enrichment
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2020-35570?

CVE-2020-35570 is a medium vulnerability published on February 16, 2021. An issue was discovered in MB connect line mymbCONNECT24, mbCONNECT24 and Helmholz myREX24 and myREX24.virtual through 2.11.2. An unauthenticated attacker is able to access files (that should have been restricted) via forceful browsing.

When was CVE-2020-35570 disclosed?

CVE-2020-35570 was first published in the National Vulnerability Database on February 16, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-35570 actively exploited?

CVE-2020-35570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 74.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-35570?

CVE-2020-35570 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2020-35570?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-35570, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-35570

Explore →

Is Your Infrastructure Affected by CVE-2020-35570?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-35570

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-35570?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)