Quick answers
- Is CVE-2026-114443 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114443 being exploited in the wild.
- How severe is CVE-2026-114443?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- CleanTalk Security by CleanTalk before 2.191.
- Is there a fix for CVE-2026-114443?
- Yes: fixed in 2.191. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114443 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-114443?
- Check whether you run CleanTalk Security by CleanTalk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.191
Technical details
The plugin accepts a two-factor authenticator code at login without verifying the account password first, violating authentication best practices. This is a broken authentication bypass (CWE-287) requiring only the time-based authenticator code and the target username; no password is needed. An attacker who gains access to a user's authenticator device or intercepts the code can assume their identity.
Affected products
- CleanTalk Security by CleanTalk before 2.191
Timeline
- 2026-10-28: disclosed
- 2026-10-30: advisory