CVE-2024-8632

KB Support – WordPress Help Desk and Knowledge Base <= 1.6.6 - Missing Authorization to Unauthenticated Ticket Reply Exposure

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

Strategic Overview

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

At a glance

CVE-2024-8632 is a medium-severity Missing Authorization vulnerability in the KB Support WordPress plugin, affecting versions <= 1.6.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. 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 access and modification of data due to a missing capability check on the 'kbs_ajax_load_front_end_replies' and 'kbs_ajax_mark_reply_as_read' functions in all versions up to, and including, 1.6.6. This makes it possible for unauthenticated attackers to read replies of any ticket, and mark any reply as read.

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

KB Support <= 1.6.6 carries this weakness at kbs_ajax_load_front_end_replies, and reaching it takes no account at all. 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. 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