CVE-2025-66204: WBCE_CMS · Improper Restriction of Excessive Authentication Attempts
Affects WBCE_CMSSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.6.5 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.5
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade wbce/WBCE_CMS to 1.6.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubwbce/WBCE_CMSpkg:github/wbce/WBCE_CMSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, affected organizations should immediately upgrade WBCE CMS to version 1.6.5 or later, where the issue is fixed. In addition, organizations should implement server-side validation of the X-Forwarded-For header, ensuring it is only trusted when coming from known and secure reverse proxies or load balancers. If possible, disable reliance on client-controlled headers for authentication rate limiting. Employ additional brute-force protection mechanisms such as account lockouts based on user identifiers rather than IP addresses, CAPTCHA challenges after multiple failed attempts, and multi-factor authentication (MFA) to reduce the risk of credential compromise. Monitoring and alerting on unusual login patterns and failed authentication attempts can help detect exploitation attempts. Network-level protections such as web application firewalls (WAFs) can also be configured to detect and block suspicious header manipulation. Finally, enforce strong password policies and conduct regular security awareness training to reduce the risk of successful brute-force attacks.
Description
WBCE CMS is a content management system. Version 1.6.4 contains a brute-force protection bypass where an attacker can indefinitely reset the counter by modifying `X-Forwarded-For` on each request, gaining unlimited password guessing attempts, effectively bypassing all brute-force protection. The application fully trusts the `X-Forwarded-For` header without validating it or restricting its usage. This issue is fixed in version 1.6.5.