CVE-2024-8548

KB Support – WordPress Help Desk and Knowledge Base <= 1.6.6 - Missing Authorization to Authenticated (Subscriber+) Multiple Administrator Actions

2024-09-30 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 1.6.7
Affected Version
<= 1.6.6
CVSS
8.1High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-8548
View all KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin vulnerabilities

At a glance

CVE-2024-8548 is a high-severity Missing Authorization vulnerability in the KB Support WordPress plugin, affecting versions <= 1.6.6. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.6.7; sites on affected versions should update now. Disclosed September 2024, reported by Krzysztof Zając.

Vulnerability Overview

The KB Support – WordPress Help Desk and Knowledge Base plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on several functions in the /includes/ajax-functions.php file all versions up to, and including, 1.6.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform multiple administrative actions, such as replying to arbitrary tickets, updating the status of any post, deleting any post, adding notes to tickets, flagging or unflagging tickets, and adding or removing ticket participants.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

CWE-862: Missing Authorization

Reaching this weakness in KB Support <= 1.6.6 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 KB Support the fix is 1.6.7: builds <= 1.6.6 are affected, anything from 1.6.7 onward is not.

Remediation

Update to version 1.6.7, 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: KB Support 1.6.7 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