|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 critical, was found in SeaCMS 7.2. This affects an unknown code of the file member.php?mod=repsw4. The manipulation as part of a Request leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
SeaCMS 7.2 mishandles member.php?mod=repsw4 requests.
The bug was discovered 01/06/2019. The weakness was presented 02/17/2019. This vulnerability is uniquely identified as CVE-2019-8418 since 02/17/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/11/2020).
The vulnerability was handled as a non-public zero-day exploit for at least 42 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Privilege escalation
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
02/17/2019 +42 days 🔍
02/17/2019 +0 days 🔍
02/18/2019 +1 days 🔍
05/11/2020 +448 days 🔍
SourcesStatus: Not defined
CVE: CVE-2019-8418 (🔍)
EntryCreated: 02/18/2019 09:37 AM
Updated: 05/11/2020 06:56 AM
Changes: (1) vulnerability_discoverydate
Do you want to use VulDB in your project?
Use the official API to access entries easily!