Vulnerability in WordPress (CVE-2025-10745)
Summary
Vulnerability in WordPress (CVE-2025-10745). Risk of unauthorized operations or information disclosure. Exploitable via banhammer_secret_key.
Original description
The description as published by the source.
The Banhammer – Monitor Site Traffic, Block Bad Users and Bots plugin for WordPress is vulnerable to Blocking Bypass in all versions up to, and including, 3.4.8. This is due to a site-wide “secret key” being deterministically generated from a constant character set using md5() and base64_encode() and then stored in the banhammer_secret_key option. This makes it possible for unauthenticated attackers to bypass the plugin’s logging and blocking by appending a GET parameter named banhammer-process_{SECRET} where {SECRET} is the predictable value, thereby causing Banhammer to abort its protections for that request.
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-10745 has been found in WordPress.
Attackers can target a specific entry point like banhammer_secret_key over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2025-10745" on the vendor's site.
CVE-2025-10745 (WordPress) — CWE-330 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: banhammer_secret_key
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-330) exists in WordPress. Attackers reach the vulnerable code path via banhammer_secret_key without authentication.
Check the vendor advisory for the affected versions of WordPress. Attack surface: banhammer_secret_key.
Severity: Medium (CVSS 5.3/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 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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。