CVSS 3.1
4.3 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NCVE-2026-121612 wpzoom wpbruiser {no- captcha anti-spam}: Weak Authentication
Medium (4.3) in wpzoom wpbruiser {no- captcha anti-spam}. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
Weak Authentication vulnerability in WPZOOM WPBruiser {no- Captcha anti-Spam} goodbye-captcha allows Authentication Abuse.This issue affects WPBruiser {no- Captcha anti-Spam}: from n/a through 3.6.2.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-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.
- CWE
- CWE-1390 Weak Authentication
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-121612 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121612?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121612?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-2026-121612 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.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-121612)
HTML:
<a href="https://cve.bz/cve/CVE-2026-121612"><img src="https://cve.bz/cve/badge/CVE-2026-121612.svg" alt="CVE-2026-121612"></a>
Affected
- wpzoom:wpbruiser {no- captcha anti-spam}
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| WPZOOM WPBruiser {no- Captcha anti-Spam} | through 3.6.2 |
Fixed in
| Product | Fixed in |
|---|---|
| WPZOOM WPBruiser {no- Captcha anti-Spam} | 3.6.3 |
Fix and patched versions
- WPZOOM WPBruiser {no- Captcha anti-Spam}: fixed in 3.6.3