CVE-2024-40519

CVE-2024-40519 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

Description

SeaCMS 12.9 has a remote code execution vulnerability. The vulnerability is caused by admin_smtp.php directly splicing and writing the user input data into weixin.php without processing it, which allows authenticated attackers to exploit the vulnerability to execute arbitrary commands and obtain system permissions.

Frequently asked questions

What is CVE-2024-40519?
SeaCMS 12.9 has a remote code execution vulnerability. The vulnerability is caused by admin_smtp.php directly splicing and writing the user input data into weixin.php without processing it, which allows authenticated attackers to exploit the vulnerability to execute arbitrary commands and obtain system permissions.
How severe is CVE-2024-40519?
CVE-2024-40519 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-2024-40519 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-40519?
CVE-2024-40519 affects Seacms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-40519?
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.
Does CVE-2024-40519 have an EU (EUVD) identifier?
Yes. CVE-2024-40519 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-38498.
When was CVE-2024-40519 published?
CVE-2024-40519 was published on 2024-07-12 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Seacms

All CVEs affecting Seacms →