WordPress is a free and open-source content management syste… (CVE-2021-39201)

Summary

Vulnerability reported (CVE-2021-39201). Risk of unauthorized operations or information disclosure. Exploitable via unfiltered_html.

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) NVD GitHub Advisory 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 CVE-2021-39201 has been found.
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: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2021-39201" on the vendor's site.

CVE-2021-39201
Attack vector: remote (network-reachable)
Attack surface: unfiltered_html
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) has been reported. Attackers reach the vulnerable code path via unfiltered_html.

📍 Affected scope

Check the vendor advisory for the affected versions. Attack surface: unfiltered_html.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami wordpress-multisite

[{"type":"SEMVER","events":[{"introduced":"5.0.0"},{"fixed":"5.8.0"}]}]

Bitnami wordpress

[{"type":"SEMVER","events":[{"introduced":"5.0.0"},{"fixed":"5.8.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2021-39201 wordpress Fixed in: 5.7.3+dfsg1-0+deb11u1
Ubuntu UBUNTU-CVE-2021-39201 wordpress

References

advisory github.com
advisory debian.org
web hackerone.com
web nvd.nist.gov