Security readout for executives and security teams
Plain-English summary
Fiyo CMS 2.0.7 contains SQL injection risk in its article list controller. The issue is tied to several GET parameters. For an organization still running this CMS version, the concern is possible database manipulation or data exposure, but the provided sources do not give severity scoring, a vendor advisory, or confirmed exploitation.
Executive priority
Treat this as a targeted remediation item for any legacy Fiyo CMS estate. It is not KEV-listed, but SQL injection in a CMS can affect sensitive content and database integrity if reachable.
Technical view
The CVE describes SQL injection in `dapur/apps/app_article/controller/article_list.php` through `cat`, `user`, `level`, and dynamic `iSortCol_$i` GET parameters. The source bundle identifies Fiyo CMS 2.0.7 and a GitHub issue reference, but provides no CVSS, CWE, patch version, or exploitation confirmation.
Likely exposure
Exposure is most likely limited to organizations running Fiyo CMS 2.0.7 with the vulnerable article list controller reachable by users or attackers. The bundle does not establish broader version ranges, authentication requirements, or internet-wide prevalence.
Exploitation context
CISA KEV is false for this CVE, and the provided bundle does not cite active exploitation. SQL injection is generally serious, but exploitability details are incomplete here, including access requirements and database impact.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, affected range, or remediation details are provided. Analysis should stay scoped to Fiyo CMS 2.0.7 and the named controller parameters unless upstream issue evidence proves more.
Mitigation direction
- Check Fiyo CMS upstream guidance and issue #5 for any fixed release or patch reference.
- Upgrade away from Fiyo CMS 2.0.7 if a maintained fixed version is confirmed.
- Restrict access to the vulnerable CMS controller where business operations allow.
- Review logs for unusual requests using the named GET parameters.
- Consider migration if no maintained vendor fix can be confirmed.
Validation and detection
- Inventory public and internal systems for Fiyo CMS 2.0.7.
- Confirm whether `article_list.php` exists at the cited path.
- Review code handling of `cat`, `user`, `level`, and `iSortCol_$i`.
- Check whether any applied local patches sanitize or parameterize these inputs.
- Look for log entries targeting the cited controller and parameters.
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-11418 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/5CVE 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.
