Security readout for executives and security teams
Plain-English summary
BigTree CMS through version 4.2.18 has an authenticated SQL injection issue. A logged-in user with access to the developer module could manipulate database-related input and execute unintended SQL. This can threaten site data integrity and confidentiality, but the public sources do not provide CVSS scoring or evidence of active exploitation.
Executive priority
Prioritize remediation if BigTree CMS is still used and non-admin authenticated users can access developer tooling. The issue can affect database integrity, but urgency is tempered by authentication requirements and limited public evidence.
Technical view
The CVE describes SQL injection in core\admin\modules\developer\modules\designer\form-create.php. A remote authenticated attacker creates a crafted table name at admin/developer/modules/designer/, with the issue visible through admin/dashboard/vitals-statistics/integrity/check/?external=true. The source bundle names BigTree CMS through 4.2.18 as affected.
Likely exposure
Exposure is likely limited to BigTree CMS deployments through 4.2.18 where authenticated users can access the admin developer module or module designer functionality.
Exploitation context
No CISA KEV listing or cited source indicates active exploitation. The available evidence describes an authenticated SQL injection path, not unauthenticated internet-wide exploitation.
Researcher notes
The public record is sparse: no CVSS, CWE, CPE, patch version, or exploitation evidence is included in the bundle. Treat the path details as sensitive validation indicators, not exploitation instructions.
Mitigation direction
- Identify any BigTree CMS installations and confirm their exact versions.
- Review BigTree CMS vendor guidance for the fixed or supported upgrade path.
- Restrict admin and developer-module access to trusted users only.
- Use least-privilege database credentials for the CMS application account.
- Monitor database and admin logs for unusual table-name or integrity-check activity.
Validation and detection
- Confirm whether BigTree CMS version is 4.2.18 or earlier.
- Review user roles with access to admin/developer/modules/designer/.
- Check logs for requests to the cited form-create and integrity-check paths.
- Inspect database logs for unexpected schema changes or suspicious SQL errors.
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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-9427 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/288CVE 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.