Security readout for executives and security teams
Plain-English summary
BigTree CMS versions through 4.2.18 can let an authenticated remote user disrupt revision saving by using XSS-like content in a revision name. This is mainly an availability and workflow risk for sites relying on CMS revisions, not evidence of full system compromise.
Executive priority
Treat this as a limited but real CMS operations risk. Prioritize if BigTree is internet-accessible or many users have editor/admin access.
Technical view
The CVE describes a flaw in BigTree admin.php where XSS sequences in revision names can cause denial of service by preventing revisions from being saved. The source bundle does not provide CVSS, CWE, fixed-version details, or evidence of unauthenticated exploitation.
Likely exposure
Exposure is limited to BigTree CMS deployments through 4.2.18 where untrusted or lower-trust authenticated users can access revision naming workflows.
Exploitation context
No cited source indicates active exploitation, and the CVE is not listed as KEV in the provided bundle. Exploitation requires authenticated remote access and affects revision-saving availability.
Researcher notes
Evidence is sparse: the CVE text and linked GitHub issue identify the affected component, version range, authentication requirement, and denial-of-service outcome. No CVSS, CWE, patch version, or exploitation evidence is provided.
Mitigation direction
- Inventory BigTree CMS deployments and identify versions through 4.2.18.
- Check BigTree vendor guidance or release notes for fixed versions.
- Restrict CMS admin access to trusted users only.
- Review permissions for accounts that can create or rename revisions.
- Monitor CMS errors related to failed revision saves.
Validation and detection
- Confirm whether any BigTree CMS instance is version 4.2.18 or earlier.
- Review who has authenticated access to revision workflows.
- Check application logs for repeated revision save failures.
- Verify vendor guidance before approving remediation status.
- Test fixes only in staging with non-destructive inputs.
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-9546 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/298CVE reference · x_refsource_CONFIRM
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.