Fiyo CMS 2.0.7 /system/site.php $_REQUEST['link'] sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Fiyo CMS 2.0.7 and classified as critical. This issue affects some unknown processing of the file /system/site.php. Performing a manipulation of the argument $_REQUEST['link'] as part of Request results in sql injection. This vulnerability is cataloged as CVE-2017-17102. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as critical has been found in Fiyo CMS 2.0.7 (Content Management System). This affects an unknown part of the file /system/site.php. The manipulation of the argument $_REQUEST['link'] as part of a Request 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 /system/site.php via $_REQUEST['link'].
The bug was discovered 12/03/2017. The weakness was shared 12/04/2017 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-17102 since 12/03/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:system/site.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-110171 and VDB-110170 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/03/2017 🔍12/03/2017 🔍
12/04/2017 🔍
12/04/2017 🔍
12/04/2017 🔍
01/25/2021 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2017-17102 (🔍)
GCVE (CVE): GCVE-0-2017-17102
GCVE (VulDB): GCVE-100-110169
See also: 🔍
Entry
Created: 12/04/2017 15:04Updated: 01/25/2021 17:21
Changes: 12/04/2017 15:04 (45), 12/12/2019 06:25 (7), 01/25/2021 17:21 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.