Fiyo CMS 2.0.7 comment_status.php $_GET['id'] sql injection

Summaryinfo

A vulnerability marked as critical has been reported in Fiyo CMS 2.0.7. The impacted element is an unknown function of the file dapur/apps/app_article/controller/comment_status.php. Performing a manipulation of the argument $_GET['id'] as part of Comment results in sql injection. This vulnerability is reported as CVE-2017-11413. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, was found in Fiyo CMS 2.0.7 (Content Management System). This affects an unknown code of the file dapur/apps/app_article/controller/comment_status.php. The manipulation of the argument $_GET['id'] as part of a Comment leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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

The bug was discovered 07/17/2017. The weakness was disclosed 07/18/2017 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-11413 since 07/17/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:dapur/apps/app_article/controller/comment_status.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-103736, VDB-103738, VDB-103739 and VDB-103740 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Fiyo

Name

• CMS

Version

• 2.0.7

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion