CVE-2017-15808
In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php.
Does this matter?
A public exploit is published in Exploit-DB and the impact is high, while EPSS rates exploitation at 1.2%. Anyone can run this; patch or mitigate before the next change window and check exposed instances for signs of use.
Description
In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php.
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 1.17% probability · 67th percentile
- Public exploits
- 1 in Exploit-DB · first 3 December 2025
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Affected
- phpmyfaq/phpmyfaq
- Source
- cve@mitre.org
EPSS 1.2% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
Public exploits (1)
Entries in Exploit-DB that cite this CVE. Links go to the Exploit-DB page and to the file in the public repository; nothing is hosted here. A verified tick means the Exploit-DB team confirmed the exploit works against the stated version.
References
- https://github.com/MarkLee131/awesome-web-pocs/blob/main/CVE-2017-15808.md
- https://github.com/thorsten/phpMyFAQ/commit/a249b4645fb86f6a9fbe5d2344ab1cbdb906b75cIssue Tracking, Patch, Third Party Advisory
- https://github.com/thorsten/phpMyFAQ/commit/a249b4645fb86f6a9fbe5d2344ab1cbdb906b75cIssue Tracking, Patch, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.