LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11631: dapur/app/app_user/controller/status.php in Fiyo CMS 2.0.7 has SQL injection via the id parameter.

dapur/app/app_user/controller/status.php in Fiyo CMS 2.0.7 has SQL injection via the id parameter.

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-11631 is a reported SQL injection in Fiyo CMS 2.0.7. An unsafe id parameter in a status controller could let attacker-supplied input affect database queries. The source bundle does not provide CVSS severity, confirmed exploit activity, or a named fixed release.

Executive priority

Prioritize confirmation if any Fiyo CMS 2.0.7 system remains in service. Treat internet-facing instances as urgent because SQL injection can threaten data confidentiality and integrity, even though severity data is incomplete.

Technical view

The reported flaw is in dapur/app/app_user/controller/status.php in Fiyo CMS 2.0.7, where the id parameter is vulnerable to SQL injection. The CVE record is sparse: no CVSS vector, CWE, complete CPE data, or remediation details are supplied.

Likely exposure

Exposure is most likely limited to organizations still running Fiyo CMS 2.0.7, especially if the affected CMS interface is reachable by untrusted users. The structured affected-product data is incomplete, so version inventory is required.

Exploitation context

The source bundle includes a public GitHub issue reference, but it does not show CISA KEV listing or other evidence of active exploitation. Public disclosure means defenders should assume the issue is knowable, but not claim observed exploitation.

Researcher notes

The record is minimal. The description names the file, parameter, product, and version, but lacks CVSS, CWE, CPEs, patch details, and exploit-status evidence. Avoid broad product claims beyond Fiyo CMS 2.0.7 unless additional sources verify them.

Mitigation direction

  • Inventory Fiyo CMS deployments and identify any version 2.0.7 instances.
  • Review the linked FiyoCMS issue and vendor/project guidance for remediation status.
  • Upgrade, replace, or retire affected Fiyo CMS instances if no maintained fix is available.
  • Restrict access to the affected CMS interface to trusted users and networks.
  • Review database account privileges used by the CMS and reduce unnecessary permissions.

Validation and detection

  • Confirm whether dapur/app/app_user/controller/status.php exists in deployed instances.
  • Verify the running Fiyo CMS version from trusted administrative or deployment records.
  • Review web and application logs for unusual id parameter activity or database errors.
  • Use authorized, non-destructive testing in staging to confirm remediation.
  • Document whether the system is internet-facing, authenticated-only, or internally restricted.
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-11631 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.