phpMyFAQ up to 2.9.8 admin/ajax.config.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in phpMyFAQ up to 2.9.8. Affected is an unknown function of the file admin/ajax.config.php. Executing a manipulation can lead to cross-site request forgery. This vulnerability is registered as CVE-2017-15808. It is possible to launch the attack remotely. Furthermore, an exploit is available. The affected component should be upgraded.
Details
A vulnerability has been found in phpMyFAQ up to 2.9.8 (Content Management System) and classified as problematic. This vulnerability affects an unknown part of the file admin/ajax.config.php. The manipulation with an unknown input 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. CVE summarizes:
In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php.
The bug was discovered 10/23/2017. The weakness was published 10/23/2017 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability was named CVE-2017-15808 since 10/23/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:admin/ajax.config.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.9.9 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (52455). Similar entry is available at VDB-108581. Once again VulDB remains the best source 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.4
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: phpMyFAQ 2.9.9
Patch: github.com
Timeline
10/23/2017 🔍10/23/2017 🔍
10/23/2017 🔍
10/23/2017 🔍
10/24/2017 🔍
12/10/2025 🔍
Sources
Advisory: a249b4645fb86f6a9fbe5d2344ab1cbdb906b75cStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2017-15808 (🔍)
GCVE (CVE): GCVE-0-2017-15808
GCVE (VulDB): GCVE-100-108580
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 10/24/2017 11:09Updated: 12/10/2025 11:00
Changes: 10/24/2017 11:09 (62), 11/30/2019 13:43 (2), 01/04/2023 14:07 (5), 04/16/2025 17:55 (19), 12/10/2025 11:00 (9)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.