How severe is CVE-2019-8418?

CVE-2019-8418 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-8418 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-8418?

CVE-2019-8418 affects Seacms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-8418?

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-2019-8418 published?

CVE-2019-8418 was published on 2019-02-17 and last updated on 2026-06-17.

CVE-2019-8418

CVE-2019-8418 is a high-severity vulnerability in Seacms 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.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 4.0
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Seacms
Published: 2019-02-17
Last modified: 2026-06-17

Description

SeaCMS 7.2 mishandles member.php?mod=repsw4 requests.

Frequently asked questions

What is CVE-2019-8418?: SeaCMS 7.2 mishandles member.php?mod=repsw4 requests.
How severe is CVE-2019-8418?: CVE-2019-8418 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-8418 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-8418?: CVE-2019-8418 affects Seacms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-8418?: 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-2019-8418 published?: CVE-2019-8418 was published on 2019-02-17 and last updated on 2026-06-17.

References

https://github.com/seacms/seacms-v7.2/issues/2

Affected products (1)

cpe:2.3:a:seacms:seacms:7.2:*:*:*:*:*:*:*

More vulnerabilities in Seacms

CVE-2025-44073 — Critical (CVSS 9.8): SeaCMS v13.3 was discovered to contain a SQL injection vulnerability via the component admin_comment_news.php.
CVE-2025-44074 — Critical (CVSS 9.8): SeaCMS v13.3 was discovered to contain a SQL injection vulnerability via the component admin_topic.php.
CVE-2025-44072 — Critical (CVSS 9.8): SeaCMS v13.3 was discovered to contain a SQL injection vulnerability via the component admin_manager.php.
CVE-2025-44071 — Critical (CVSS 9.8): SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component phomebak.php. This…
CVE-2025-29647 — Critical (CVSS 9.8): SeaCMS v13.3 has a SQL injection vulnerability in the component admin_tempvideo.php.
CVE-2025-25521 — Critical (CVSS 9.8): Seacms <=13.3 is vulnerable to SQL Injection in admin_type_news.php.

All CVEs affecting Seacms →