Unauthenticated protection bypass via predictable secret key
Published Sep 26, 2025 · Updated Sep 26, 2025
Blocking bypass in Banhammer 3.4.8 and earlier allows remote attackers to evade traffic logging and access blocks via a crafted request. The plugin derives the site-wide banhammer_secret_key from a constant character set with md5() and base64_encode(), making its value reproducible. Appending banhammer-process_{SECRET} as a GET parameter makes Banhammer stop processing that unauthenticated request, so both logging and configured bans are skipped.
Summary
What happened
Blocking bypass in Banhammer 3.4.8 and earlier allows remote attackers to evade traffic logging and access blocks via a crafted request. The plugin derives the site-wide banhammer_secret_key from a constant character set with md5() and base64_encode(), making its value reproducible. Appending banhammer-process_{SECRET} as a GET parameter makes Banhammer stop processing that unauthenticated request, so both logging and configured bans are skipped.
The record
- CVE
- CVE-2025-10745
- Published
- Sep 26, 2025
- Updated
- Sep 26, 2025
- Vendor
- Plugin Planet
- Product
- Banhammer – Monitor Site Traffic, Block Bad Users and Bots
- Classifications
- CWE-330, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2025CVE publishedPublication date reported by the CVE source.
- Sep 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=3.4.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo