WordPress up to 5.5.1 FilteredIterator.php deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in WordPress up to 5.5.1. Affected by this vulnerability is an unknown functionality of the file wp-includes/Requests/Utility/FilteredIterator.php. Such manipulation leads to deserialization. This vulnerability is documented as CVE-2020-28032. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in WordPress up to 5.5.1 (Content Management System). It has been rated as critical. Affected by this issue is an unknown functionality of the file wp-includes/Requests/Utility/FilteredIterator.php. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability.
The weakness was released 11/03/2020. The advisory is available at wpscan.com. This vulnerability is handled as CVE-2020-28032. Technical details are known, but there is no available exploit.
By approaching the search of inurl:wp-includes/Requests/Utility/FilteredIterator.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 5.5.2 eliminates this vulnerability. Applying a patch 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: 🔍
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WordPress 5.5.2
Patch: github.com
Timeline
10/31/2020 🔍11/03/2020 🔍
11/03/2020 🔍
12/01/2020 🔍
Sources
Product: wordpress.comAdvisory: wpscan.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-28032 (🔍)
GCVE (CVE): GCVE-0-2020-28032
GCVE (VulDB): GCVE-100-164186
Entry
Created: 11/03/2020 08:42Updated: 12/01/2020 10:41
Changes: 11/03/2020 08:42 (40), 12/01/2020 10:36 (2), 12/01/2020 10:41 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.