dbcve.org
Kb SupportWordPress extension · Logon

CVE-2024-33589

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-29
Fix available
A fix is available. Upgrade to 1.6.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in WPOmnia KB Support.This issue affects KB Support: from n/a through 1.6.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing Authorization vulnerability in KB Support plugin for WordPress allows authenticated users (with at least subscriber-level access) to perform actions or access resources that should require higher privileges. This is a classic broken access control issue where the plugin fails to verify user capabilities before allowing access to sensitive support ticket or knowledge base functions.

MitigationUpdate KB Support to the latest version which includes proper capability checks (current_user_can() verification) on all AJAX handlers and admin pages. Until then, restrict user registration and monitor for suspicious access patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Kb SupportWordPress extension
Affected:< 1.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm KB Support plugin is installed
    Go to WordPress admin dashboard > Plugins > Installed Plugins and look for 'KB Support' or check the plugin files in /wp-content/plugins/kb-support/ for the main PHP file
    Affected if KB Support plugin is present in the WordPress installation
  2. Identify installed version
    Check the plugin version in the plugin header at /wp-content/plugins/kb-support/ or view the plugin details in the WordPress plugins admin page
    Affected if Version is lower than 1.6.1 (the affected range is anything below this version)
  3. Verify if user registration is enabled
    Navigate to WordPress Settings > General > Membership and check 'Anyone can register' - also check if new user default role is set to something above 'Subscriber'
    Affected if Anyone can register is enabled and/or default role is set to Subscriber or higher with the plugin installed
  4. Check for publicly accessible AJAX handlers
    Inspect the plugin's main PHP file for AJAX action hooks (add_action('wp_ajax_...')) that do not include current_user_can() or capability checks before processing requests
    Affected if AJAX handlers exist without capability verification (requires code review of the plugin source)
  5. Review admin page access controls
    Check if plugin admin pages/controllers verify user capabilities using current_user_can() or similar WordPress capability checks before displaying sensitive ticket or knowledge base data
    Affected if Admin pages load without capability verification for low-privilege users (requires code review)

User is affected if KB Support version is below 1.6.1, user registration is open allowing subscriber-level access, and the plugin exposes unauthenticated or low-privilege-accessible AJAX handlers or admin pages without capability verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.6.1 or later
Fixed in 1.6.1
Interim mitigation

Update KB Support to the latest version which includes proper capability checks (current_user_can() verification) on all AJAX handlers and admin pages. Until then, restrict user registration and monitor for suspicious access patterns.

Recommended fix High confidence

KB Support version 1.6.1

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate KB Support in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.6.1
  5. Verify the plugin version shows 1.6.1 or higher after updating
  6. Test the affected functionality to confirm the authorization vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kb Support Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33589 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data