LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11354: Fiyo CMS v2.0.7 has an SQL injection vulnerability in dapur/apps/app_article/sys_article.php via the name p...

Fiyo CMS v2.0.7 has an SQL injection vulnerability in dapur/apps/app_article/sys_article.php via the name parameter in editing or adding a tag name.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Fiyo CMS 2.0.7 is reported to have SQL injection in article tag creation or editing. If an exposed site runs this version, a malicious tag name could affect database queries. Sources do not provide CVSS, confirmed exploitation, or a named patch, so urgency depends on whether this CMS and feature are deployed.

Executive priority

Treat as a targeted remediation item, not a confirmed emergency. Prioritize quickly if Fiyo CMS 2.0.7 is internet-facing or used on business-critical sites; otherwise track through normal legacy CMS risk reduction.

Technical view

CVE-2017-11354 describes SQL injection in `dapur/apps/app_article/sys_article.php` through the `name` parameter when adding or editing a tag name in Fiyo CMS 2.0.7. The source bundle provides one public issue reference and no CVSS vector, CWE mapping, exploit confirmation, or remediation details.

Likely exposure

Exposure is likely limited to organizations still running Fiyo CMS 2.0.7 with reachable article tag add/edit functionality. The sources do not clarify authentication requirements, internet exposure, or affected later versions.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not confirm active exploitation. A public GitHub issue is cited, but evidence is incomplete on exploit maturity, access requirements, and real-world abuse.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, patch version, or authentication details are provided. Avoid assuming unauthenticated exploitation or broad product impact. Validate against actual Fiyo CMS deployments and the referenced issue.

Mitigation direction

  • Inventory sites and repositories for Fiyo CMS 2.0.7 usage.
  • Check Fiyo CMS vendor or project guidance for a fixed release or workaround.
  • Restrict administrative and tag-editing paths to trusted users and networks.
  • Review database backups and recovery plans for affected CMS instances.
  • Monitor CMS and database logs for suspicious tag add or edit activity.

Validation and detection

  • Confirm whether any production system runs Fiyo CMS 2.0.7.
  • Verify whether article tag add/edit functionality is enabled or reachable.
  • Review `sys_article.php` handling of the tag `name` parameter.
  • Check whether installed updates mention this CVE or the affected file.
  • Look for unusual database errors or unexpected tag records around CMS activity.
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-11354 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.