phpMyFAQ up to 2.9.8 Tag admin/tags.main.php cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in phpMyFAQ up to 2.9.8. Affected by this vulnerability is an unknown functionality of the file admin/tags.main.php of the component Tag Handler. The manipulation leads to cross site scripting. This vulnerability is documented as CVE-2017-15809. The attack can be initiated remotely. There is not any 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/tags.main.php of the component Tag Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:
In phpMyFaq before 2.9.9, there is XSS in admin/tags.main.php via a crafted tag.
The bug was discovered 10/23/2017. The weakness was released 10/23/2017 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-15809 since 10/23/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. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:admin/tags.main.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.9.9 eliminates this vulnerability.
Entry connected to this vulnerability is available at VDB-108580. If you want to get the best quality for vulnerability data then you always have to consider 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: 4.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.8
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 |
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/23/2017 🔍10/23/2017 🔍
10/23/2017 🔍
10/23/2017 🔍
10/24/2017 🔍
01/04/2023 🔍
Sources
Advisory: cb648f0d5690b81647dd5c9efe942ebf6cce7da9Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-15809 (🔍)
GCVE (CVE): GCVE-0-2017-15809
GCVE (VulDB): GCVE-100-108581
See also: 🔍
Entry
Created: 10/24/2017 11:09Updated: 01/04/2023 14:08
Changes: 10/24/2017 11:09 (63), 11/30/2019 13:49 (2), 01/04/2023 14:08 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.