CVE-2024-10531

Kognetiks Chatbot for WordPress <= 2.1.7 - Missing Authorization to Authenticated (Subscriber+) Assistant Update

2024-11-12 00:00
Tieu Pham Trong Nhan

Strategic Overview

Status
Patched in 2.1.8
Affected Version
<= 2.1.7
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10531
View all Kognetiks Chatbot for WordPress vulnerabilities

At a glance

CVE-2024-10531 is a medium-severity Missing Authorization vulnerability in the Kognetiks Chatbot for WordPress WordPress plugin, affecting versions <= 2.1.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.8; sites on affected versions should update now. Disclosed November 2024, reported by Tieu Pham Trong Nhan.

Vulnerability Overview

The Kognetiks Chatbot for WordPress plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the update_assistant() function in all versions up to, and including, 2.1.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to update GTP assistants.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Kognetiks Chatbot for WordPress <= 2.1.7 carries this weakness at update_assistant(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Kognetiks Chatbot for WordPress the fix is 2.1.8: builds <= 2.1.7 are affected, anything from 2.1.8 onward is not.

Remediation

Update to version 2.1.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Kognetiks Chatbot for WordPress 2.1.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C