dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-13604

HIGH · 7.5 CVSS v3.1 Published 2025-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.7.4 via the 'kbs' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads/kbs directory which can contain file attachments included in support tickets. The vulnerability was partially patched in version 1.7.3.2.

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 · high confidence

The KB Support WordPress plugin stores support ticket file attachments in an unsecured /wp-content/uploads/kbs directory that can be accessed by unauthenticated attackers, allowing extraction of sensitive customer data and attachments without authentication.

MitigationUpgrade the KB Support plugin to the latest version and verify that the /wp-content/uploads/kbs directory has proper access controls to prevent unauthenticated access.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installation and version
    In WordPress admin, navigate to Plugins > Installed Plugins and locate KB Support to view the installed version number, or inspect the main plugin PHP file for the version constant
    Affected if KB Support plugin is installed and the version falls within the affected range (versions prior to the security fix)
  2. Verify the uploads/kbs directory exists
    Check the server file system for the presence of /wp-content/uploads/kbs/ directory using a file manager, FTP, or SSH
    Affected if the /wp-content/uploads/kbs directory exists and contains ticket attachment files
  3. Test unauthenticated directory access
    Attempt to directly access the directory via web browser or curl: curl -I https://yourdomain.com/wp-content/uploads/kbs/
    Affected if the directory is accessible without authentication and lists or serves files directly
  4. Check for access control files
    Inspect the /wp-content/uploads/kbs/ directory for index.php or .htaccess files that should deny direct access
    Affected if no index.php or .htaccess protection exists, allowing unrestricted file access

A user is affected if they have KB Support installed with an unpatched version AND the /wp-content/uploads/kbs directory is directly accessible without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the KB Support plugin to the latest version and verify that the /wp-content/uploads/kbs directory has proper access controls to prevent unauthenticated access.

Recommended fix Moderate confidence

KB Support plugin version 1.7.5

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Locate KB Support plugin in the list
  4. 4. Check if current version is below 1.7.5 (the fully patched release)
  5. 5. If update available, click 'Update Now' to upgrade to version 1.7.5
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/kb-support and upload manually
  7. 7. Verify the /wp-content/uploads/kbs directory is not directly accessible by visiting that URL in a browser

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13604 — 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-13604 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