LiveActive security incident?Get immediate response
CVE Record

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

Fiyo CMS 2.0.7 has SQL injection in dapur/apps/app_article/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

CVE-2017-11413 is a reported SQL injection in Fiyo CMS 2.0.7. If an exposed installation accepts untrusted input in the affected comment-status controller, an attacker may be able to interfere with database-backed content or data. The provided sources do not include a CVSS score, patch status, or active exploitation evidence.

Executive priority

Treat this as an exposure-discovery item unless Fiyo CMS 2.0.7 is confirmed in production. If present and internet-facing, prioritize remediation because SQL injection can affect data confidentiality and integrity.

Technical view

The CVE describes SQL injection in `dapur/apps/app_article/controller/comment_status.php` through the `$_GET['id']` parameter in Fiyo CMS 2.0.7. The bundle does not define authentication requirements, route exposure, exact query behavior, CVSS, CWE, CPEs, or fixed versions.

Likely exposure

Likely limited to organizations still running Fiyo CMS 2.0.7, especially where the affected `dapur` article comment-status functionality is reachable. Exposure cannot be confirmed from the supplied metadata alone.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. A public GitHub issue is referenced, but the bundle does not establish exploit maturity, public weaponization, or exploitation in the wild.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, fixed version, authentication context, or exploit telemetry is provided. Analysis should center on confirming reachability of the named controller and whether the `id` input reaches SQL without safe parameterization.

Mitigation direction

  • Inventory any Fiyo CMS installations and confirm whether version 2.0.7 is present.
  • Check the FiyoCMS project issue and vendor guidance for a fixed release or official patch.
  • Restrict access to administrative or `dapur` paths where operationally possible.
  • Review database permissions for the CMS account and reduce unnecessary privileges.
  • Monitor web and database logs for abnormal requests involving the `id` parameter.

Validation and detection

  • Confirm whether `dapur/apps/app_article/controller/comment_status.php` exists in deployed code.
  • Verify the deployed Fiyo CMS version against asset inventory and source files.
  • Review route exposure and authentication controls for the affected controller.
  • Check whether local code or vendor updates sanitize the `id` parameter safely.
  • Review recent logs for suspicious errors or unusual comment-status requests.
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-11413 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.