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.
0.5%(unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-12-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-307Improper Restriction of Excessive Authentication Attempts CWE-693Protection Mechanism Failure
Show the promptExplain CVE-2025-66204 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-66204?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-66204?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-66204 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
lukasz-rybak/CVE-2025-66204Harbor Check: matches CVE0 stars, created CVE-2025-66204 - WBCE CMS allows brute-force protection bypass using X-Forwarded-For header
Attack patterns (CAPEC)
CAPEC-16 Dictionary-based Password Attack Likelihood: Medium · Severity: High
CAPEC-49 Password Brute Forcing Likelihood: Medium · Severity: High
CAPEC-560 Use of Known Domain Credentials Likelihood: High · Severity: High
CAPEC-565 Password Spraying Likelihood: High · Severity: High
CAPEC-600 Credential Stuffing Likelihood: High · Severity: High
CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
CAPEC-653 Use of Known Operating System Credentials Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).