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

Summary

Vulnerability in wordpress (DEBIAN-CVE-2024-31210). Successful exploitation can lead to full system takeover. Exploitable via uploads. Mitigation: upgrade to 5.7.11+dfsg1-0+deb11u1 or later.

Original description

The description as published by the source.

WordPress is an open publishing platform for the Web. It's possible for a file of a type other than a zip file to be submitted as a new plugin by an administrative user on the Plugins -> Add New -> Upload Plugin screen in WordPress. If FTP credentials are requested for installation (in order to move the file into place outside of the uploads directory) then the uploaded file remains temporary available in the Media Library despite it not being allowed. If the DISALLOW_FILE_EDIT constant is set to true on the site and FTP credentials are required when uploading a new theme or plugin, then this technically allows an RCE when the user would otherwise have no means of executing arbitrary PHP code. This issue only affects Administrator level users on single site installations, and Super Admin level users on Multisite installations where it's otherwise expected that the user does not have permission to upload or execute arbitrary PHP code. Lower level users are not affected. Sites where the DISALLOW_FILE_MODS constant is set to true are not affected. Sites where an administrative user either does not need to enter FTP credentials or they have access to the valid FTP credentials, are not affected. The issue was fixed in WordPress 6.4.3 on January 30, 2024 and backported to versions 6.3.3, 6.2.4, 6.1.5, 6.0.7, 5.9.9, 5.8.9, 5.7.11, 5.6.13, 5.5.14, 5.4.15, 5.3.17, 5.2.20, 5.1.18, 5.0.21, 4.9.25, 2.8.24, 4.7.28, 4.6.28, 4.5.31, 4.4.32, 4.3.33, 4.2.37, and 4.1.40. A workar…

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

DEBIAN-CVE-2024-31210 (wordpress)
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: uploads / DISALLOW_FILE_EDIT / true / DISALLOW_FILE_MODS
Patched: 5.7.11+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.

❓ What is the problem

A vulnerability (unclassified) exists in wordpress. Attackers reach the vulnerable code path via uploads without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of wordpress. Attack surface: uploads / DISALLOW_FILE_EDIT / true / DISALLOW_FILE_MODS.

🔥 Severity

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

🔧 How to fix

Update to 5.7.11+dfsg1-0+deb11u1.

🛡️ 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 5.7.11+dfsg1-0+deb11u1
```
ステージング環境で 5.7.11+dfsg1-0+deb11u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 wordpress

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

Debian:12 wordpress

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

Debian:13 wordpress

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

Debian:14 wordpress

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

References

advisory security-tracker.debian.org