LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11412: Fiyo CMS 2.0.7 has SQL injection in dapur/apps/app_comment/controller/comment_status.php via $_GET['id'].

Fiyo CMS 2.0.7 has SQL injection in dapur/apps/app_comment/controller/comment_status.php via $_GET['id'].

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Fiyo CMS 2.0.7 contains a reported SQL injection in the comment status controller. In business terms, a vulnerable deployment could expose site database data or allow data changes, depending on application privileges. The public sources do not provide CVSS, authentication requirements, a vendor fix, or evidence of active exploitation.

Executive priority

Treat this as a targeted legacy CMS risk. Prioritize discovery first, then isolate or upgrade affected systems. Urgency rises if Fiyo CMS 2.0.7 is internet-facing or handles sensitive site data.

Technical view

CVE-2017-11412 reports SQL injection in dapur/apps/app_comment/controller/comment_status.php through the GET id parameter in Fiyo CMS 2.0.7. The source bundle names no CWE, CPE, patch, or mitigation. KEV status is false, so active exploitation is not established by the provided evidence.

Likely exposure

Likely limited to organizations still running Fiyo CMS 2.0.7 with the affected comment status controller reachable. Internet exposure, authentication requirements, and default route availability are not stated in the sources.

Exploitation context

The issue is publicly referenced in a GitHub issue and CVE records. The provided sources do not show exploit-in-the-wild activity, inclusion in CISA KEV, or reliable exploit maturity details.

Researcher notes

Evidence is sparse. The CVE identifies the vulnerable file and parameter, but not exploit prerequisites, impact boundaries, patch status, or vulnerable CPEs. Avoid assuming unauthenticated reachability without route and access-control validation.

Mitigation direction

  • Inventory any Fiyo CMS deployments and confirm whether version 2.0.7 is present.
  • Check FiyoCMS project or vendor guidance for fixed versions or official remediation.
  • Restrict access to dapur/admin-style CMS paths until remediation is confirmed.
  • Retire or isolate unsupported Fiyo CMS instances if no maintained fix is available.
  • Review database permissions used by the CMS and reduce unnecessary privileges.

Validation and detection

  • Confirm whether dapur/apps/app_comment/controller/comment_status.php exists in deployed code.
  • Verify whether comment status routes are externally reachable or require authentication.
  • Perform source review for unsafe handling of the GET id parameter.
  • Review web logs for unusual requests targeting comment_status.php or id values.
  • Document affected instances, exposure path, and remediation status.
Prepared
Confidence
medium
Sources
3

Public sources used

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-11412 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.