Radar sectionsDatabase
Check my site
WordPress plugin

Security by CleanTalk <= 2.190 — Unauthenticated Authentication Bypass

CVE-2026-114443Published · Updated

Action summary

Affected: ≤2.190Update to 2.191 or newer

All remediation steps
Severity
High8.1
CVSS
8.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:H Attack complexity
High
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-287 Improper Authentication
Required access
No account needed
Exploit prediction (EPSS)
0.2% chance in 30 days8th percentile
CISA KEV
Not listed

Am I affected?

Security Plugin, Firewall & Malware Scanner with Auto Removal security-malware-firewall

  1. Affected≤ 2.190
  2. Patched in2.191

Update to 2.191 or newer.

You are affected if you run ≤ 2.190. Version 2.191 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Security Plugin, Firewall & Malware Scanner with Auto Removal.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.191, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Security Plugin, Firewall & Malware Scanner with Auto Removal to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Karthik.

The Security by CleanTalk plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in all versions up to, and including, 2.190. This is due to missing verification that the first authentication factor (password) had been successfully completed before accepting a submitted authenticator-app or email two-factor code, allowing the second factor to be submitted in isolation. This makes it possible for unauthenticated attackers to log in as any user who has two-factor authentication enabled, including administrators, by supplying only a valid TOTP code without knowing the account password. Two-factor authentication must be enabled for the targeted user account.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Security Plugin, Firewall & Malware Scanner with Auto Removal

All 8
More vulnerabilities in Security Plugin, Firewall & Malware Scanner with Auto Removal
SeverityVulnerabilityCVEPublished
Low2.7Authenticated (Administrator+) Information Exposure
≤2.190Update to 2.191
CVE-2026-114444
High7.5Unauthenticated SQL Injection
≤2.184Update to 2.185
CVE-2026-66593
High7.2Unauthenticated Stored Cross-Site Scripting via Page URL
≤2.168Update to 2.169
CVE-2025-13604
Critical9.8Unauthenticated Arbitrary File Upload
≤2.149Update to 2.150
CVE-2024-13365
High7.5Authorization Bypass via Reverse DNS Spoofing to Unauthenticated SQL Injection
≤2.145Update to 2.145.1
CVE-2024-10570

Timeline

  1. CVE published

    Severity high, CVSS 8.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?