Security readout for executives and security teams
Plain-English summary
This issue lets an authenticated BigTree CMS user delete their own account even though deletion was intended to be administrator-only. The business risk is mainly loss of administrative control over user offboarding, backups, audit retention, and timing-sensitive account handling.
Executive priority
Treat as a low-priority governance and access-control fix unless BigTree CMS supports regulated workflows or important audit retention. Address during normal patch cycles.
Technical view
BigTree CMS through 4.2.18 lacked authorization enforcement preventing self-deletion by non-admin users. The source bundle does not provide CVSS, CWE, exploit details, or a named fixed release, but it cites a GitHub issue and corrective commit.
Likely exposure
Exposure is likely limited to BigTree CMS deployments through 4.2.18 where authenticated users can access account-management deletion behavior.
Exploitation context
The bundle does not show active exploitation, and the CVE is not listed as KEV. Evidence supports an authenticated authorization flaw affecting the current user’s own account, not arbitrary user deletion.
Researcher notes
The core issue is improper authorization around self-account deletion. The bundle is incomplete on severity scoring, CWE classification, exact fixed release, and exploit availability, so avoid extrapolating beyond authenticated self-deletion impact.
Mitigation direction
- Check whether any BigTree CMS instance is running version 4.2.18 or earlier.
- Review the referenced vendor commit and apply the vendor-supported fix or later maintained release.
- Restrict account deletion actions to administrators until the fix is confirmed.
- Preserve account records and backups according to retention requirements before user deletion.
Validation and detection
- Confirm non-admin users cannot delete their own accounts after remediation.
- Review access logs for unexpected self-deletion events by authenticated users.
- Verify administrator-only authorization checks cover user deletion workflows.
- Confirm operational documentation covers backup and retention steps before account removal.
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-9378 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/282CVE reference · x_refsource_MISC
- https://github.com/bigtreecms/BigTree-CMS/commit/f7899701d7be91b7dc546b65e44a27b668eb3b76CVE 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.