phpMyFAQ up to 2.9.8 admin/stat.adminlog.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in phpMyFAQ up to 2.9.8. Affected by this issue is some unknown functionality of the file admin/stat.adminlog.php. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2017-15731. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in phpMyFAQ up to 2.9.8 (Content Management System) and classified as problematic. This issue affects an unknown code of the file admin/stat.adminlog.php. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.adminlog.php.
The bug was discovered 10/02/2017. The weakness was shared 10/22/2017 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-15731 since 10/21/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 20 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin/stat.adminlog.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.9.9 eliminates this vulnerability.
The entries VDB-108333, VDB-108332, VDB-108331 and VDB-108330 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.3
VulDB Temp Score: 3.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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 |
OpenVAS ID: 801936
OpenVAS Name: phpMyFAQ Multiple XSS And CSRF Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: phpMyFAQ 2.9.9
Patch: github.com
Timeline
10/02/2017 🔍10/21/2017 🔍
10/22/2017 🔍
10/22/2017 🔍
10/23/2017 🔍
01/04/2023 🔍
Sources
Advisory: fadb9a70b5f7624a6926b8834d5c6001c210f09cStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-15731 (🔍)
GCVE (CVE): GCVE-0-2017-15731
GCVE (VulDB): GCVE-100-108329
See also: 🔍
Entry
Created: 10/23/2017 09:11Updated: 01/04/2023 10:42
Changes: 10/23/2017 09:11 (63), 11/28/2019 15:36 (1), 01/19/2021 13:10 (2), 01/04/2023 10:42 (4)
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.