WordPress WPBruiser {no- Captcha anti-Spam} plugin <= 3.6.2 - Broken Authentication vulnerability

published 2026-11-09 8h ago modified 2026-11-09 7h ago also EUVD-2026-120115

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

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.

Patch / fix

fixed in 1

WPZOOM WPBruiser {no- Captcha anti-Spam} 3.6.3

Is CVE-2026-121612 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 8h ago (2026-11-09)

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected products

WPZOOM WPBruiser {no- Captcha anti-Spam}

Classification

Weakness

CWE-1390 Weak Authentication

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/goodbye-captcha/vulnerability/wordpress-wpbruiser-no-captcha-anti-spam-plugin-3-6-2
vdb-entry

Sources

CVE List CVE-2026-121612
NVD CVE-2026-121612

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.