phpMyFAQ up to 2.9.6 inc/PMF/Faq.php question cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in phpMyFAQ up to 2.9.6. This affects an unknown part of the file inc/PMF/Faq.php. Executing a manipulation of the argument question can lead to cross site scripting. This vulnerability is tracked as CVE-2017-7579. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in phpMyFAQ up to 2.9.6 (Content Management System). This vulnerability affects an unknown function of the file inc/PMF/Faq.php. The manipulation of the argument question with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:
inc/PMF/Faq.php in phpMyFAQ before 2.9.7 has XSS in the question field.
The bug was discovered 04/02/2017. The weakness was disclosed 04/07/2017 (Website). The advisory is available at phpmyfaq.de. This vulnerability was named CVE-2017-7579 since 04/07/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 are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:inc/PMF/Faq.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.9.7 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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 scriptingCWE: CWE-79 / CWE-94 / CWE-74
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: phpMyFAQ 2.9.7
Patch: github.com
Timeline
04/02/2017 🔍04/07/2017 🔍
04/07/2017 🔍
04/07/2017 🔍
04/08/2017 🔍
11/27/2022 🔍
Sources
Advisory: a69f32175c28af1b34e5df83000f830e60f6bce9Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-7579 (🔍)
GCVE (CVE): GCVE-0-2017-7579
GCVE (VulDB): GCVE-100-99442
OSVDB: - CVE-2017-7579 - PhpMyFAQ - Cross-Site Scripting Issue
Entry
Created: 04/08/2017 10:25Updated: 11/27/2022 14:56
Changes: 04/08/2017 10:25 (59), 08/27/2020 16:13 (3), 11/27/2022 14:56 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.