Loading vulnerability…
WBCE CMS 1.6.4 implements brute-force protection using a per-client counter keyed on the client IP address, but it fully trusts the user-supplied X-Forwarded-For header to determine that IP. An attacker can bypass the lockout/rate-limiting mechanism by changing the X-Forwarded-For value on each authentication attempt, causing the application to treat each request as coming from a different client and effectively resetting/avoiding the brute-force counter indefinitely. This enables unlimited password guessing attempts against protected login endpoints. The issue is fixed in WBCE CMS 1.6.5.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
X-Forwarded-For from direct client connections: only accept/overwrite X-Forwarded-For at a trusted reverse proxy/load balancer, strip inbound X-Forwarded-For headers from untrusted sources, and configure the web stack to use the actual source IP (or a validated proxy header mechanism) for rate limiting/lockout decisions. Additionally, enforce rate limiting and account lockout at the reverse proxy/WAF layer independent of application headers.Patch, then assume compromise.
X-Forwarded-For.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.