CVE-2019-8908

CVE-2019-8908 is a critical-severity vulnerability in Wtcms Project Wtcms with a CVSS 3.x base score of 9.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-706.

Key facts

Description

An issue was discovered in WTCMS 1.0. It allows remote attackers to execute arbitrary PHP code by going to the "Setting -> Mailbox configuration -> Registration email template" screen, and uploading an image file, as demonstrated by a .php filename and the "Content-Type: image/gif" header.

Frequently asked questions

What is CVE-2019-8908?
An issue was discovered in WTCMS 1.0. It allows remote attackers to execute arbitrary PHP code by going to the "Setting -> Mailbox configuration -> Registration email template" screen, and uploading an image file, as demonstrated by a .php filename and the "Content-Type: image/gif" header.
How severe is CVE-2019-8908?
CVE-2019-8908 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-8908 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-2019-8908?
CVE-2019-8908 affects Wtcms Project Wtcms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-8908?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2019-8908 published?
CVE-2019-8908 was published on 2019-02-18 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Wtcms Project Wtcms

All CVEs affecting Wtcms Project Wtcms →

Other CWE-706 vulnerabilities

Browse all CWE-706 vulnerabilities →