|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability, which was classified as problematic, has been found in thorsten phpmyfaq up to 3.1.7 (Content Management System). This issue affects some unknown processing. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The software 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:
Cross-site Scripting (XSS) - Stored in GitHub repository thorsten/phpmyfaq prior to 3.1.8.
The weakness was shared 10/31/2022. It is possible to read the advisory at huntr.dev. The identification of this vulnerability is CVE-2022-3765 since 10/31/2022. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
Upgrading to version 3.1.8 eliminates this vulnerability. Applying the patch 372428d02a08e90b3a253ba5c506cda84581a5af is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔒
CNA Base Score: 8.2
CNA Vector (huntr.dev): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Cross site scripting
CWE: CWE-79 / CWE-74 / CWE-707
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: phpmyfaq 3.1.8
Timeline10/31/2022 Advisory disclosed
10/31/2022 +0 days CVE reserved
10/31/2022 +0 days VulDB entry created
11/26/2022 +26 days VulDB last update
CVE: CVE-2022-3765 (🔒)
EntryCreated: 10/31/2022 06:05 PM
Updated: 11/26/2022 04:35 PM
Changes: 10/31/2022 06:05 PM (52), 11/26/2022 04:28 PM (2), 11/26/2022 04:35 PM (11)
Do you know our Splunk app?
Download it now for free!