Virim Plugin 0.4 on WordPress Deserialization graph.php s_values/t_values/c_values deserialization
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
9.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Virim Plugin 0.4 on WordPress. It has been declared as critical. This vulnerability affects unknown code of the file graph.php of the component Deserialization. The manipulation of the argument s_values/t_values/c_values leads to deserialization. This vulnerability was named CVE-2019-12240. The attack can be initiated remotely. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability was found in Virim Plugin 0.4 on WordPress (WordPress Plugin). It has been classified as very critical. This affects an unknown part of the file graph.php of the component Deserialization. The manipulation of the argument s_values/t_values/c_values
with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Virim plugin 0.4 for WordPress allows Insecure Deserialization via s_values, t_values, or c_values in graph.php.
The weakness was published 05/20/2019. This vulnerability is uniquely identified as CVE-2019-12240 since 05/20/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of 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 09/23/2023).
By approaching the search of inurl:graph.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/20/2019 🔍05/20/2019 🔍
05/21/2019 🔍
09/23/2023 🔍
Sources
Advisory: dumpco.reStatus: Not defined
CVE: CVE-2019-12240 (🔍)
GCVE (CVE): GCVE-0-2019-12240
GCVE (VulDB): GCVE-100-135285
Entry
Created: 05/21/2019 07:40 AMUpdated: 09/23/2023 10:08 AM
Changes: 05/21/2019 07:40 AM (37), 06/14/2020 08:03 AM (18), 09/23/2023 10:08 AM (3)
Complete: 🔍
Cache ID: 18:947:40
No comments yet. Languages: en.
Please log in to comment.