Security readout for executives and security teams
Plain-English summary
CVE-2017-9379 describes multiple cross-site request forgery issues in BigTree CMS through 4.2.18. An attacker may be able to trick an authenticated administrator into triggering dashboard 404-statistics actions. The source bundle does not provide CVSS, confirmed exploit activity, or a named vendor fix.
Executive priority
Treat this as an exposure-confirmation item unless BigTree CMS is business-critical or internet-administered. The available evidence supports concern but not emergency status, because severity, exploitation, and patch details are absent from the bundle.
Technical view
The CVE cites CSRF affecting the clear parameter in core/admin/modules/dashboard/vitals-statistics/404/clear.php and the from/to parameters in core/admin/modules/dashboard/vitals-statistics/404/create-301.php. Exposure appears limited to BigTree CMS versions through 4.2.18, but the structured affected-product data is incomplete.
Likely exposure
Organizations running BigTree CMS through 4.2.18 may be exposed, especially where administrators use the CMS while browsing untrusted content. The source bundle lists vendor and product as n/a, so asset matching should rely on CMS name and version evidence.
Exploitation context
No KEV listing is present, and the provided sources do not state active exploitation. CSRF generally requires an authenticated user with relevant privileges to be induced into making an unwanted request, so practical risk depends on admin behavior and interface exposure.
Researcher notes
The CVE description is specific about files and parameters but sparse on impact. Avoid assuming data destruction or redirect abuse beyond the named clear and create-301 actions. Validate against local code and upstream issue context before assigning severity.
Mitigation direction
- Check BigTree CMS project guidance for fixed versions or workarounds.
- Identify and prioritize BigTree CMS instances through version 4.2.18.
- Restrict administrative access while remediation status is confirmed.
- Ensure administrators avoid untrusted links while authenticated to the CMS.
- Review application CSRF protections for the cited admin endpoints.
Validation and detection
- Inventory BigTree CMS deployments and confirm exact versions.
- Check whether installations are version 4.2.18 or earlier.
- Review admin routing for the cited 404 statistics endpoints.
- Confirm whether CSRF tokens or equivalent controls protect those actions.
- Document whether vendor guidance identifies a fixed release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-9379 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/bigtreecms/BigTree-CMS/issues/287CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.