# CVE-2024-8548: Missing authorization in KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin

> Authenticated subscribers can perform administrative actions like deleting posts and modifying tickets due to missing capability checks in the KB Support plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2cjx-jpg9-5gqm

## What is CVE-2024-8548?

CVE-2024-8548 is a high-severity missing authorization vulnerability in logoninc KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin, published on 1 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-8548?

It affects 1 product.


Products: Logon Kb Support.

## How do I fix CVE-2024-8548?

No fix has been published for CVE-2024-8548 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-8548 being exploited?

There is no known exploitation of CVE-2024-8548 in the wild and no public exploit code.

## Other vulnerabilities in logoninc KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin

- [CVE-2023-25983](https://insights.sbomify.com/CVE-2023-25983/): WordPress KB Support Plugin <= 1.5.84 is vulnerable to CSV Injection (high 8.8)
- [CVE-2024-8632](https://insights.sbomify.com/CVE-2024-8632/): Missing authorization in KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin (medium 6.5)
- [CVE-2024-33589](https://insights.sbomify.com/CVE-2024-33589/): WordPress KB Support plugin <= 1.6.0 - Broken Access Control vulnerability (medium 6.5)
- [CVE-2025-24741](https://insights.sbomify.com/CVE-2025-24741/): WordPress KB Support plugin <= 1.6.7 - Open Redirection vulnerability (medium 4.7)
- [CVE-2023-37890](https://insights.sbomify.com/CVE-2023-37890/): WordPress KB Support Plugin <= 1.5.88 is vulnerable to Broken Access Control (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8548 and fix it if it is affected.

What it is: CVE-2024-8548 is a high-severity missing authorization vulnerability in logoninc KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin, published on 1 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8548 in the wild and no public exploit code.

Affected product: logoninc KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8548/ (Markdown: https://insights.sbomify.com/CVE-2024-8548/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8548
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8548
- OSV: https://osv.dev/vulnerability/CVE-2024-8548

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8548/
Summaries are generated and may contain mistakes; the official description above is the record.