WordPress up to 5.2.2 pluggable.php wp_validate_redirect
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in WordPress up to 5.2.2. This impacts the function wp_validate_redirect of the file wp-includes/pluggable.php. This manipulation causes redirect.
This vulnerability is tracked as CVE-2019-16220. The attack is possible to be carried out remotely. No exploit exists.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in WordPress up to 5.2.2 (Content Management System). It has been declared as critical. Affected by this vulnerability is the function wp_validate_redirect of the file wp-includes/pluggable.php. The manipulation with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In WordPress before 5.2.3, validation and sanitization of a URL in wp_validate_redirect in wp-includes/pluggable.php could lead to an open redirect.
The weakness was disclosed 09/11/2019 (Website). It is possible to read the advisory at seclists.org. This vulnerability is known as CVE-2019-16220 since 09/11/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.
By approaching the search of inurl:wp-includes/pluggable.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 5.2.3 eliminates this vulnerability.
The entries VDB-141664, VDB-141665, VDB-141666 and VDB-141668 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.1
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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: RedirectCWE: CWE-601
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.2.3
Patch: github.com
Timeline
09/11/2019 🔍09/11/2019 🔍
09/12/2019 🔍
08/21/2024 🔍
Sources
Product: wordpress.comAdvisory: c86ee39ff4c1a79b93c967eb88522f5c09614a28
Status: Not defined
CVE: CVE-2019-16220 (🔍)
GCVE (CVE): GCVE-0-2019-16220
GCVE (VulDB): GCVE-100-141667
See also: 🔍
Entry
Created: 09/12/2019 08:28Updated: 08/21/2024 18:55
Changes: 09/12/2019 08:28 (58), 08/21/2020 09:15 (1), 12/19/2023 10:42 (5), 12/19/2023 10:47 (1), 08/21/2024 18:55 (15)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.