WordPress up to 5.3.0 HTML5 wp-includes/kses.php wp_kses_bad_protocol input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WordPress up to 5.3.0. It has been rated as critical. This impacts the function wp_kses_bad_protocol of the file wp-includes/kses.php of the component HTML5 Handler. This manipulation causes input validation.
This vulnerability is registered as CVE-2019-20041. Remote exploitation of the attack is possible. No exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability was found in WordPress up to 5.3.0 (Content Management System). It has been declared as very critical. Affected by this vulnerability is the function wp_kses_bad_protocol of the file wp-includes/kses.php of the component HTML5 Handler. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
wp_kses_bad_protocol in wp-includes/kses.php in WordPress before 5.3.1 mishandles the HTML5 colon named entity, allowing attackers to bypass input sanitization, as demonstrated by the javascript: substring.
The weakness was published 12/27/2019. This vulnerability is known as CVE-2019-20041 since 12/27/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 12/27/2019).
By approaching the search of inurl:wp-includes/kses.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 5.3.1 eliminates this vulnerability.
Similar entries are available at VDB-147807 and VDB-147806. If you want to get the best quality for vulnerability data then you always have to consider 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: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
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: Input validationCWE: 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.3.1
Patch: github.com
Timeline
12/27/2019 🔍12/27/2019 🔍
12/27/2019 🔍
03/17/2024 🔍
Sources
Product: wordpress.comAdvisory: b1975463dd995da19bb40d3fa0786498717e3c53
Status: Not defined
CVE: CVE-2019-20041 (🔍)
GCVE (CVE): GCVE-0-2019-20041
GCVE (VulDB): GCVE-100-147805
See also: 🔍
Entry
Created: 12/27/2019 18:01Updated: 03/17/2024 14:39
Changes: 12/27/2019 18:01 (39), 12/27/2019 18:06 (18), 03/17/2024 14:38 (6), 03/17/2024 14:39 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.