KindEditor 4.1.x Google Editor uploadbutton.html cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in KindEditor 4.1.x and classified as problematic. Affected is an unknown function of the file inurl:/examples/uploadbutton.html of the component Google Editor. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2021-42228. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in KindEditor 4.1.x. It has been classified as problematic. This affects an unknown part of the file inurl:/examples/uploadbutton.html of the component Google Editor. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity.
The weakness was published 10/14/2021 as 337. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-42228 since 10/11/2021. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
By approaching the search of inurl:inurl:/examples/uploadbutton.html it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/11/2021 🔍10/14/2021 🔍
10/14/2021 🔍
10/20/2021 🔍
Sources
Advisory: 337Status: Confirmed
CVE: CVE-2021-42228 (🔍)
GCVE (CVE): GCVE-0-2021-42228
GCVE (VulDB): GCVE-100-184425
Entry
Created: 10/14/2021 21:21Updated: 10/20/2021 15:27
Changes: 10/14/2021 21:21 (38), 10/20/2021 15:27 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.