| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in WordPress. This issue affects some unknown processing of the component Block Editor. Executing a manipulation can lead to neutralization. This vulnerability is tracked as CVE-2020-11030. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability has been found in WordPress (Content Management System) and classified as problematic. This vulnerability affects an unknown code block of the component Block Editor. The manipulation with an unknown input leads to a neutralization vulnerability. The CWE definition for the vulnerability is CWE-707. The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component. As an impact it is known to affect integrity. CVE summarizes:
In affected versions of WordPress, a special payload can be crafted that can lead to scripts getting executed within the search block of the block editor. This requires an authenticated user with the ability to add content. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33).
The weakness was disclosed 04/30/2020 (GitHub Repository). The advisory is available at github.com. This vulnerability was named CVE-2020-11030 since 03/30/2020. The attack can be initiated remotely. The requirement for exploitation is a single authentication. The technical details are unknown and an exploit is not available.
Upgrading to version 5.4.1 eliminates this vulnerability.
The entries VDB-154641, VDB-154640, VDB-154639 and VDB-154638 are pretty similar. 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: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.0
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.4
NVD Vector: 🔍
CNA Base Score: 6.4
CNA Vector (GitHub, Inc.): 🔍
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: NeutralizationCWE: CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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.4.1
Timeline
03/30/2020 🔍04/30/2020 🔍
05/01/2020 🔍
06/04/2024 🔍
Sources
Product: wordpress.comAdvisory: GHSA-vccm-6gmc-qhjh
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-11030 (🔍)
GCVE (CVE): GCVE-0-2020-11030
GCVE (VulDB): GCVE-100-154642
See also: 🔍
Entry
Created: 05/01/2020 08:56Updated: 06/04/2024 18:52
Changes: 05/01/2020 08:56 (39), 05/01/2020 09:01 (12), 10/14/2020 16:27 (1), 10/14/2020 16:34 (1), 06/04/2024 18:44 (17), 06/04/2024 18:52 (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.