Vulnerability in WordPress (CVE-2025-11734)
Summary
Vulnerability in WordPress (CVE-2025-11734). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /wp-json/aioseoBrokenLinkChecker/v1/post.
Original description
The description as published by the source.
The Broken Link Checker by AIOSEO – Easily Fix/Monitor Internal and External links plugin for WordPress is vulnerable to unauthorized post modification due to missing authorization in all versions up to, and including, 1.2.5. This is due to the plugin registering a REST API endpoint that only checks for a broad capability (aioseo_blc_broken_links_page) that is granted to contributor level users, without verifying the user's permission to perform actions on the specific post being targeted. This makes it possible for authenticated attackers, with contributor level access and above, to trash arbitrary posts via the DELETE /wp-json/aioseoBrokenLinkChecker/v1/post endpoint.
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-2025-11734 has been found in WordPress.
Attackers can target a specific entry point like DELETE /wp-json/aioseoBrokenLinkChecker/v1/post over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2025-11734" on the vendor's site.
CVE-2025-11734 (WordPress) — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /wp-json/aioseoBrokenLinkChecker/v1/post
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-862) exists in WordPress. Attackers reach the vulnerable code path via DELETE /wp-json/aioseoBrokenLinkChecker/v1/post.
Check the vendor advisory for the affected versions of WordPress. Attack surface: DELETE /wp-json/aioseoBrokenLinkChecker/v1/post.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
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 DELETE /wp-json/aioseoBrokenLinkChecker/v1/post requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'DELETE /wp-json/aioseoBrokenLinkChecker/v1/post' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /wp-json/aioseoBrokenLinkChecker/v1/postへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against DELETE /wp-json/aioseoBrokenLinkChecker/v1/post on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。