dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-13567

HIGH · 7.5 CVSS v3.1 Published 2025-04-01
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 Awesome Support – WordPress HelpDesk & Support Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.3.1 via the 'awesome-support' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads/awesome-support directory which can contain file attachments included in support tickets. The vulnerability was partially patched in version 6.3.1.

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 Awesome Support WordPress plugin fails to restrict access to the /wp-content/uploads/awesome-support directory, allowing unauthenticated attackers to directly browse and download file attachments submitted with support tickets. This exposes sensitive customer data, communications, and potentially credentials or personal information included in ticket attachments.

MitigationImplement proper access controls to require authentication before serving files from the awesome-support upload directory, or configure the web server to deny direct access (e.g., via .htaccess rules) while allowing authorized ticket access through the plugin's protected download handler.

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. Verify Awesome Support plugin is installed
    Check your WordPress plugins directory or use wp-cli: wp plugin list --status=active --format=csv | grep awesome-support
    Affected if The plugin is active on the site
  2. Confirm the upload directory exists
    Check if /wp-content/uploads/awesome-support/ directory exists on the web server filesystem
    Affected if The upload directory exists and is being used for ticket attachments
  3. Test unauthenticated directory access
    Send an HTTP GET request to http://[yourdomain]/wp-content/uploads/awesome-support/ without any authentication cookies or headers
    Affected if The directory listing or files are returned without requiring login (HTTP 200 rather than 401/403)
  4. Test unauthenticated file download
    Attempt to directly download a known or guessed file path within the awesome-support upload directory using a browser or curl without authentication
    Affected if Files download successfully without authentication being enforced

If the Awesome Support plugin is active and the upload directory is directly accessible without authentication, the environment is affected by this vulnerability.

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

Implement proper access controls to require authentication before serving files from the awesome-support upload directory, or configure the web server to deny direct access (e.g., via .htaccess rules) while allowing authorized ticket access through the plugin's protected download handler.

Recommended fix Moderate confidence

Latest version beyond 6.3.1 (likely 6.3.2 or later)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the 'Awesome Support' plugin and check the current version.
  4. 4. If the current version is 6.3.1 or lower, update the plugin to the latest available version.
  5. 5. Verify the update completed successfully and test that the plugin functions correctly.
  6. 6. Ensure the /wp-content/uploads/awesome-support directory has proper access controls - consider reviewing file permissions and confirming directory browsing is disabled at the server level as an additional hardening measure.

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

Have this fixed 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 help mitigating

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-13567 — 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-13567 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