CVE-2017-9379

CVE-2017-9379 is a high-severity vulnerability in Bigtreecms Bigtree Cms 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

Multiple CSRF issues exist in BigTree CMS through 4.2.18 - the clear parameter to core\admin\modules\dashboard\vitals-statistics\404\clear.php and the from or to parameter to core\admin\modules\dashboard\vitals-statistics\404\create-301.php.

Frequently asked questions

What is CVE-2017-9379?
Multiple CSRF issues exist in BigTree CMS through 4.2.18 - the clear parameter to core\admin\modules\dashboard\vitals-statistics\404\clear.php and the from or to parameter to core\admin\modules\dashboard\vitals-statistics\404\create-301.php.
How severe is CVE-2017-9379?
CVE-2017-9379 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-2017-9379 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-9379?
CVE-2017-9379 affects Bigtreecms Bigtree Cms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-9379?
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-2017-9379 published?
CVE-2017-9379 was published on 2017-06-02 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Bigtreecms Bigtree Cms

All CVEs affecting Bigtreecms Bigtree Cms →

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

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