LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11416: Fiyo CMS 2.0.7 has SQL injection in /apps/app_comment/controller/insert.php via the name parameter.

Fiyo CMS 2.0.7 has SQL injection in /apps/app_comment/controller/insert.php via the name parameter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-11416 reports SQL injection in Fiyo CMS 2.0.7 comment submission handling through the name parameter. In business terms, an exposed vulnerable site may let an attacker interfere with the CMS database. The available sources do not provide severity scoring, authentication context, active exploitation evidence, or an official fix.

Executive priority

Treat as a targeted exposure review, not a confirmed emergency. Prioritize if Fiyo CMS 2.0.7 is internet-facing or handles sensitive data, because SQL injection can affect database confidentiality and integrity.

Technical view

The CVE description identifies SQL injection in /apps/app_comment/controller/insert.php via the name parameter in Fiyo CMS 2.0.7. The source bundle includes a GitHub issue reference, but no CVSS, CWE, structured CPEs, patch version, or mitigation details. KEV is false, so active exploitation is not established by the provided sources.

Likely exposure

Exposure is most likely limited to internet-facing or reachable Fiyo CMS 2.0.7 installations with the comment insertion endpoint enabled. The structured affected-product data is incomplete, so confirm version and endpoint presence before prioritizing broad remediation.

Exploitation context

The provided sources support the existence of a SQL injection report, but not active exploitation. The bundle does not establish authentication requirements, exploit maturity, database impact scope, or whether maintained fixed releases exist.

Researcher notes

Evidence is sparse. The CVE text names the vulnerable path and parameter, but lacks CVSS, CWE, CPE, fixed-version, and exploit-context details. Avoid assuming broader Fiyo versions are affected without vendor or code evidence.

Mitigation direction

  • Inventory Fiyo CMS deployments and identify any version 2.0.7 instances.
  • Check FiyoCMS project or vendor guidance for fixed versions or official remediation.
  • Limit exposure of comment submission functionality while remediation is assessed.
  • Review database account privileges used by the CMS.
  • Plan upgrade or migration if no maintained fix is available.

Validation and detection

  • Confirm whether Fiyo CMS 2.0.7 is deployed.
  • Check whether /apps/app_comment/controller/insert.php exists and is reachable.
  • Review web logs for suspicious comment submissions or database errors.
  • Verify whether any vendor-recommended patch or upgrade has been applied.
  • Document exposed instances, owners, and remediation status.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2017-11416 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.