phpMyFAQ up to 2.9.8 ajax.attachment.php Attachment cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in phpMyFAQ up to 2.9.8. This vulnerability affects unknown code of the file admin/ajax.attachment.php. This manipulation as part of Attachment causes cross-site request forgery. This vulnerability is handled as CVE-2017-15733. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in phpMyFAQ up to 2.9.8 (Content Management System). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file admin/ajax.attachment.php. The manipulation as part of a Attachment leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/ajax.attachment.php and admin/att.main.php.
The bug was discovered 10/08/2017. The weakness was released 10/22/2017 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2017-15733 since 10/21/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin/ajax.attachment.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.9.9 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-108333, VDB-108332, VDB-108330 and VDB-108329. Statistical analysis made it clear that VulDB provides the best quality for 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/08/2017 🔍10/21/2017 🔍
10/22/2017 🔍
10/22/2017 🔍
10/23/2017 🔍
01/04/2023 🔍
Sources
Advisory: ef5a66df4bcfacc7573322af33ce10c30e0bb896Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-15733 (🔍)
GCVE (CVE): GCVE-0-2017-15733
GCVE (VulDB): GCVE-100-108331
See also: 🔍
Entry
Created: 10/23/2017 09:11Updated: 01/04/2023 10:54
Changes: 10/23/2017 09:11 (64), 11/28/2019 15:40 (2), 01/04/2023 10:54 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.