dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-13367

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Sandbox plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the export_download action in all versions up to, and including, 0.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to download an entire copy of a sandbox environment which can contain sensitive information like the wp-config.php file.

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 Sandbox plugin for WordPress is vulnerable to broken access control due to a missing capability check on the export_download action. This allows any authenticated user with Subscriber-level permissions or higher to download the entire sandbox environment, including sensitive files like wp-config.php containing database credentials and other secrets.

MitigationUpdate the Sandbox plugin to version 0.5 or later which includes the proper capability check. If immediate updating is not feasible, consider disabling the plugin or implementing web application firewall rules to restrict access to the export_download endpoint.

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
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. Verify Sandbox plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'sandbox' or 'sandbox-plugin', or look for the Sandbox plugin in the WordPress admin under Plugins > Installed Plugins
    Affected if The Sandbox plugin appears in the installed plugins list
  2. Identify the installed Sandbox plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Sandbox plugin version number displayed under the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/sandbox/ for the 'Version' tag
    Affected if The version shown is less than 0.5 (for example, 0.4.x, 0.3.x, etc.)
  3. Confirm user role configuration
    Check if there are user accounts with Subscriber-level roles or higher in WordPress under Users > All Users. The vulnerability affects any authenticated user with Subscriber, Contributor, Author, Editor, or Administrator role
    Affected if There exists at least one user account with Subscriber-level permissions or higher who is not authorized to access sandbox exports
  4. Test export_download endpoint accessibility
    If you have a test Subscriber-level user account, attempt to access the export_download action via a direct request to the endpoint (commonly /wp-admin/admin-ajax.php?action=export_download or similar). Check if the request returns sandboxed files without requiring elevated privileges
    Affected if The endpoint returns sandbox contents or wp-config.php without returning a 403 Forbidden or capability error

You are affected if the Sandbox plugin version is below 0.5 and your WordPress site has at least one authenticated user with Subscriber-level access or higher.

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

Update the Sandbox plugin to version 0.5 or later which includes the proper capability check. If immediate updating is not feasible, consider disabling the plugin or implementing web application firewall rules to restrict access to the export_download endpoint.

Recommended fix Moderate confidence

Latest version of the Sandbox plugin (newer than 0.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Sandbox' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completed successfully
  6. 6. Confirm the new version is greater than 0.4

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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