CVE-2017-5212

CRITICALNVD 9.89.8—

9.8

Open-Xchange GmbH OX App Suite 7.8.3 is affected by: Incorrect Access Control.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 68.3%
KEV: Not listed

Published

May 23, 2019

Last Modified

November 21, 2024

References (6)

cve@mitrehttp://open-xchange.com
cve@mitrehttp://ox.com
cve@mitrehttps://documentation.open-xchange.com/7.8.4/release-notes/release-notes.html
af854a3a-2127-422b-91ae-364da2661108http://open-xchange.com
af854a3a-2127-422b-91ae-364da2661108http://ox.com
af854a3a-2127-422b-91ae-364da2661108https://documentation.open-xchange.com/7.8.4/release-notes/release-notes.html

Weakness Classification(1)

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

CWE-284Improper Access Control

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-05-27 19:14 UTCEG score recompute
2026-05-27 19:14 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
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-2017-5212?

CVE-2017-5212 is a critical vulnerability published on May 23, 2019. Open-Xchange GmbH OX App Suite 7.8.3 is affected by: Incorrect Access Control.

When was CVE-2017-5212 disclosed?

CVE-2017-5212 was first published in the National Vulnerability Database on May 23, 2019, 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-2017-5212 actively exploited?

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

What is the CVSS score of CVE-2017-5212?

CVE-2017-5212 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-5212?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5212, 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-2017-5212

Explore →

Is Your Infrastructure Affected by CVE-2017-5212?

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

Start Free Scan →Browse All CVEs

CVE-2017-5212

📅 Published

🔄 Last Modified

🔗 References (6)