CVE-2018-6224

CVE-2018-6224 is a high-severity vulnerability in Trendmicro Email Encryption Gateway with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

A lack of cross-site request forgery (CSRF) protection vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to submit authenticated requests to a user browsing an attacker-controlled domain.

Frequently asked questions

What is CVE-2018-6224?
A lack of cross-site request forgery (CSRF) protection vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to submit authenticated requests to a user browsing an attacker-controlled domain.
How severe is CVE-2018-6224?
CVE-2018-6224 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-6224 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-6224?
CVE-2018-6224 affects Trendmicro Email Encryption Gateway. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-6224?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-6224 published?
CVE-2018-6224 was published on 2018-03-15 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Trendmicro Email Encryption Gateway

All CVEs affecting Trendmicro Email Encryption Gateway →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →