gVectors wpDiscuz Plugin up to 7.0.4 on WordPress wmuUploadFiles PHP File code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in gVectors wpDiscuz Plugin 7.0.0/7.0.1/7.0.2/7.0.3/7.0.4 on WordPress. Affected by this vulnerability is the function wmuUploadFiles. Executing a manipulation as part of PHP File can lead to code injection.
The identification of this vulnerability is CVE-2020-24186. The attack may be launched remotely. Furthermore, there is an exploit available.
Details
A vulnerability has been found in gVectors wpDiscuz Plugin 7.0.0/7.0.1/7.0.2/7.0.3/7.0.4 on WordPress (WordPress Plugin) and classified as critical. This vulnerability affects the function wmuUploadFiles. The manipulation as part of a PHP File leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
A Remote Code Execution vulnerability exists in the gVectors wpDiscuz plugin 7.0 through 7.0.4 for WordPress, which allows unauthenticated users to upload any type of file, including PHP files via the wmuUploadFiles AJAX action.
The weakness was shared 08/24/2020. This vulnerability was named CVE-2020-24186 since 08/13/2020. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1059.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (49962). Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 8.7
VulDB Base Score: 8.3
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 10.0
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: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/13/2020 🔍08/24/2020 🔍
08/24/2020 🔍
03/09/2025 🔍
Sources
Status: Not definedCVE: CVE-2020-24186 (🔍)
GCVE (CVE): GCVE-0-2020-24186
GCVE (VulDB): GCVE-100-160204
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/24/2020 20:17Updated: 03/09/2025 21:49
Changes: 08/24/2020 20:17 (36), 08/24/2020 20:22 (12), 11/11/2020 06:49 (1), 03/09/2025 21:49 (25)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.