CVE-2021-42228: Cross Site Request Forgery in kindeditor

kindeditor Updated 02 Oct 2025

Summary

18/10/2021
No i
High
8.8

CVE-2021-42228: Cross Site Request Forgery in kindeditor. Affects kindeditor versions < 4.1.12. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

KindEditor is an npm package that provides a Google editor for websites. It allows users to upload and edit HTML files. However, KindEditor 4.1.x is vulnerable to a Cross Site Request Forgery (CSRF) attack. This means that an attacker can upload a malicious HTML file containing CSRF code to a website using KindEditor. By tricking users into clicking a malicious link, the attacker can exploit the authority of the website to perform unauthorized actions on behalf of the user.

Vulnerability Detail

The CSRF vulnerability in KindEditor 4.1.x allows an attacker to execute unauthorized actions on a website using the authority of the website. By uploading a malicious HTML file containing CSRF code, the attacker can trick users into performing actions without their consent. This can lead to various security risks, such as unauthorized data modification, account hijacking, or spreading malware.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update KindEditor to the latest version to mitigate the CSRF risk.

Conclusion

The CSRF vulnerability in KindEditor 4.1.x poses a significant security risk as it allows attackers to perform unauthorized actions on a website. To mitigate this risk, it is essential to update KindEditor to version 4.1.13 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for kindeditor →

Share this vulnerability

FAQ

KindEditor is an npm package that provides a Google editor for websites. It allows users to upload and edit HTML files.

A CSRF vulnerability allows an attacker to perform unauthorized actions on a website using the authority of the website. By tricking users into performing actions without their consent, the attacker can exploit the vulnerability.

An attacker can upload a malicious HTML file containing CSRF code to a website using KindEditor. By tricking users into clicking a malicious link, the attacker can exploit the authority of the website to perform unauthorized actions on behalf of the user.

The potential risks of this vulnerability include unauthorized data modification, account hijacking, and spreading malware.

There is no known workaround for this vulnerability. It is crucial to update KindEditor to the latest version to mitigate the CSRF risk.

Related vulnerabilities

Recent vulnerabilities recorded for kindeditor.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback