dbcve.org
Knowledge BaseWordPress extension · Webberzone

CVE-2024-51677

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-04
Fix available
A fix is available. Upgrade to 2.2.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Ajay Knowledge Base knowledgebase allows Stored XSS.This issue affects Knowledge Base: from n/a through <= 2.2.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

A stored Cross-site Scripting (XSS) vulnerability exists in Ajay Knowledge Base plugin/theme versions up to 2.2.0. The application fails to properly neutralize user-supplied input during web page generation, allowing attackers to inject malicious scripts that are persisted on the server and executed in the browsers of other users viewing the affected pages.

MitigationImplement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML contexts. Use context-appropriate encoding (HTML entity encoding, JavaScript escaping, URL encoding) based on where the data will be displayed.

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
Knowledge BaseWordPress extension
Affected:< 2.2.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Verify Webberzone Knowledge Base plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Webberzone Knowledge Base' (may also appear as 'Ajay Knowledge Base' in older installations)
    Affected if plugin is present in the plugins list
  2. Check the installed plugin version
    Click 'View Details' on the Webberzone Knowledge Base plugin in the WordPress plugins page, or inspect the plugin's main PHP file header for the 'Version' tag
    Affected if version number is lower than 2.2.1
  3. Identify active knowledge base shortcodes or widgets
    Review pages and posts using the knowledge base shortcode (typically [knowledgebase] or similar) or knowledge base widget; check content editor for these elements
    Affected if any knowledge base functionality is in use on the site

If the Webberzone Knowledge Base plugin is installed with a version lower than 2.2.1, the site is vulnerable to stored XSS attacks via knowledge base input fields.

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 2.2.1 or later
Fixed in 2.2.1
Interim mitigation

Implement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML contexts. Use context-appropriate encoding (HTML entity encoding, JavaScript escaping, URL encoding) based on where the data will be displayed.

Recommended fix High confidence

2.2.1

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins
  3. 3. Locate the 'Knowledge Base' plugin by Ajay
  4. 4. If automatic updates are enabled, the plugin may update automatically; otherwise, click 'Update Now' to update to version 2.2.1
  5. 5. Alternatively, download version 2.2.1 from a trusted source and upload/install it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the installed version shows 2.2.1 in the Plugins list
  7. 7. Clear any caching plugins and test the Knowledge Base functionality to confirm the Stored XSS vulnerability is remediated

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

Fix this in Knowledge Base 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-51677 — 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-51677 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