Vulnerability in wordpress (DEBIAN-CVE-2024-31211)

Summary

Vulnerability in wordpress (DEBIAN-CVE-2024-31211). Successful exploitation can lead to full system takeover. Exploitable via WP_HTML_Token. Mitigation: upgrade to 6.4.2+dfsg1-1 or later.

Original description

The description as published by the source.

WordPress is an open publishing platform for the Web. Unserialization of instances of the WP_HTML_Token class allows for code execution via its __destruct() magic method. This issue was fixed in WordPress 6.4.2 on December 6th, 2023. Versions prior to 6.4.0 are not affected.

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-2024-31211 has been found in wordpress.
Attackers can target a specific entry point like WP_HTML_Token over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade wordpress to 6.4.2+dfsg1-1 or later.
If unsure, ask your IT team or search "wordpress DEBIAN-CVE-2024-31211" on the vendor's site.

DEBIAN-CVE-2024-31211 (wordpress)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: WP_HTML_Token
Patched: 6.4.2+dfsg1-1 — 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 wordpress. Attackers reach the vulnerable code path via WP_HTML_Token without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of wordpress. Attack surface: WP_HTML_Token.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 6.4.2+dfsg1-1.

🛡️ 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 '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

1
Identify exposure identify
```
grep -r 'wordpress' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wordpress を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade wordpress to 6.4.2+dfsg1-1
```
ステージング環境で 6.4.2+dfsg1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 wordpress

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.2+dfsg1-1"}]}]

Debian:14 wordpress

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.2+dfsg1-1"}]}]

References

advisory security-tracker.debian.org