Unrestricted File Upload in WordPress (CVE-2026-65640)
Summary
Vulnerability in WordPress (CVE-2026-65640). Successful exploitation can lead to full system takeover. Exploitable via upload_files.
Original description
The description as published by the source.
WordPress is vulnerable to a remote code execution vulnerability via malicious Postscript file upload by an Author level user or higher.
Prerequisites:
- Imagick and Ghostscript in use on the server
- A malicious user with the
upload_filescapability
This issue affects all versions of WordPress. Version 7.0.4 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7.
Source: NIST National Vulnerability Database NVD
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-2026-65640 has been found in WordPress.
Attackers can target a specific entry point like upload_files over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2026-65640" on the vendor's site.
CVE-2026-65640 (WordPress) — CWE-434 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: upload_files
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 (CWE-434) exists in WordPress. Attackers reach the vulnerable code path via upload_files.
Check the vendor advisory for the affected versions of WordPress. Attack surface: upload_files.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
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 し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-65640 wordpress
- Ubuntu UBUNTU-CVE-2026-65640 wordpress
References
- web wordpress.org
- web nvd.nist.gov