← Back
CVE-2022-25037
Vulnerability in @wangeditor/editor (CVE-2022-25037)
Summary
vulnerability in @wangeditor/editor (CVE-2022-25037). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `4.7.12` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-25037** has been found in @wangeditor/editor.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @wangeditor/editor to **4.7.12** or later.
If unsure, ask your IT team or search "@wangeditor/editor CVE-2022-25037" on the vendor's site.
CVE-2022-25037 (@wangeditor/editor) —
Attack vector: remote (network-reachable)
Patched: `4.7.12` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in @wangeditor/editor.
📍 Affected scope
@wangeditor/editor — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.7.12**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@wangeditor/editor' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@wangeditor/editor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@wangeditor/editor` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @wangeditor/editor to 4.7.12ステージング環境で 4.7.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@wangeditor/editor
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.7.12"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-25037
- package https://github.com/wangeditor-team/wangEditor
- web https://github.com/wangeditor-team/wangEditor/issues/3870
- web https://gist.github.com/Mdxjj/5cf0a31e8abf24ed688ceb5b3543516d
- web https://github.com/wangeditor-team/wangEditor/issues/3872
- web https://github.com/wangeditor-team/wangEditor/commit/6257a2e166346913c34ac5cfb31b6a46e9544c5a
- web https://github.com/advisories/GHSA-9hfw-cvf4-5x25