Security readout for executives and security teams
Plain-English summary
Fiyo CMS 2.0.7 contains a file deletion flaw that could let an attacker remove files outside the intended backup area. For a business, the main risk is site disruption or loss of application data if a vulnerable installation is reachable. The public sources do not confirm active exploitation or a vendor patch.
Executive priority
Treat this as a targeted remediation item for any remaining Fiyo CMS 2.0.7 deployments. Prioritize internet-facing systems and sites supporting revenue, customer access, or operational workflows.
Technical view
The CVE describes directory traversal in the file parameter during an act=db action in dapur/apps/app_config/controller/backuper.php. The reported impact is arbitrary file deletion in Fiyo CMS v2.0.7. Authentication requirements, CVSS score, affected CPEs, and fixed versions are not provided in the bundle.
Likely exposure
Exposure is most likely for organizations still running Fiyo CMS v2.0.7, especially internet-facing sites where the affected configuration or backup controller is reachable. The sources do not establish whether authentication is required.
Exploitation context
No active exploitation is cited, and the CVE is not marked in KEV. A public GitHub issue exists, so vulnerability details are publicly discoverable, but the supplied evidence does not show exploitation in the wild.
Researcher notes
The record is sparse: no CVSS, CPE, CWE, auth context, patch reference, or exploit-status evidence is supplied. Analysis should remain bounded to arbitrary file deletion via traversal in the named Fiyo CMS component.
Mitigation direction
- Check FiyoCMS project guidance for a fixed release or official workaround.
- Upgrade or retire Fiyo CMS v2.0.7 where feasible.
- Restrict access to administrative and backup-related CMS paths.
- Ensure current offline backups exist before remediation work.
- Monitor for unexpected file deletion or application integrity changes.
Validation and detection
- Inventory sites and confirm whether Fiyo CMS v2.0.7 is deployed.
- Review web server access logs for suspicious backup/config controller requests.
- Check file integrity for missing or unexpectedly changed CMS files.
- Verify administrative CMS paths are not publicly reachable.
- Document authentication and network controls protecting the affected functionality.
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.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-8853 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/FiyoCMS/FiyoCMS/issues/2CVE 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.