Vulnerability in wordpress (DEBIAN-CVE-2021-39201)
Summary
Vulnerability in wordpress (DEBIAN-CVE-2021-39201). Risk of unauthorized operations or information disclosure. Exploitable via unfiltered_html. Mitigation: upgrade to 5.7.3+dfsg1-0+deb11u1 or later.
Original description
The description as published by the source.
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. ### Impact The issue allows an authenticated but low-privileged user (like contributor/author) to execute XSS in the editor. This bypasses the restrictions imposed on users who do not have the permission to post unfiltered_html. ### Patches This has been patched in WordPress 5.8, and will be pushed to older versions via minor releases (automatic updates). It's strongly recommended that you keep auto-updates enabled to receive the fix. ### References https://wordpress.org/news/category/releases/ https://hackerone.com/reports/1142140 ### For more information If you have any questions or comments about this advisory: * Open an issue in HackerOne
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2021-39201 has been found in wordpress.
Attackers can target a specific entry point like unfiltered_html over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade wordpress to 5.7.3+dfsg1-0+deb11u1 or later.
If unsure, ask your IT team or search "wordpress DEBIAN-CVE-2021-39201" on the vendor's site.
DEBIAN-CVE-2021-39201 (wordpress)
Attack vector: remote (network-reachable)
Attack surface: unfiltered_html
Patched: 5.7.3+dfsg1-0+deb11u1 — 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.
A vulnerability (unclassified) exists in wordpress. Attackers reach the vulnerable code path via unfiltered_html.
Check the vendor advisory for the affected versions of wordpress. Attack surface: unfiltered_html.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.7.3+dfsg1-0+deb11u1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wordpress' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wordpress' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wordpressを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade wordpress to 5.7.3+dfsg1-0+deb11u1ステージング環境で 5.7.3+dfsg1-0+deb11u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org