Read the docs
TI-2022-04060 Aliases CVE-2022-4443GHSA-hgrr-97rg-c34m

BruteBank - WP Security & Firewall < 1.9 - Settings Update via CSRF

Priority MEDIUM 62Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.

Summary

The BruteBank WordPress plugin before 1.9 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00335 27th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA and NVD
Fix Fixed BruteBank (Unknown): 1.9

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownBruteBankbefore 1.91.9Patch availableCNA
  • BruteBank VendorUnknown Affected before 1.9 Fixed in 1.9 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:brutebank:brutebank:*:*:*:*:*:wordpress:*:*before 1.9VulnerableBrutebank
  • cpe:2.3:a:brutebank:brutebank:*:*:*:*:*:wordpress:*:* Versions before 1.9 Vulnerable ·Brutebank

Remediation

  • Fix · CNA BruteBank (Unknown) Fixed in 1.9

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-4443
  2. 2026-10-03 Alias added: GHSA-hgrr-97rg-c34m

References

Sources