dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-12859

HIGH · 8.8 CVSS v3.1 Published 2025-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 BoomBox Theme Extensions plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.8.0 via the 'boombox_listing' shortcode 'type' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file type can be uploaded and included.

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 BoomBox Theme Extensions WordPress plugin versions up to 1.8.0 contains a Local File Inclusion vulnerability in the 'boombox_listing' shortcode's 'type' attribute. Authenticated attackers with contributor-level or higher permissions can exploit this to include and execute arbitrary PHP files on the server, enabling code execution and potential sensitive data access.

MitigationUpdate the BoomBox Theme Extensions plugin to version 1.8.1 or later. If no update is available, disable the plugin immediately and review server logs for signs of exploitation.

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
High
Availability
High

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

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. Identify if BoomBox Theme Extensions plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BoomBox Theme Extensions' or 'BoomBox' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'boombox' or similar.
    Affected if The plugin is found in the plugins directory or listed in WordPress admin plugins page
  2. Determine the installed plugin version
    In WordPress admin Plugins page, click on the plugin name to view details, or check the main plugin file header in /wp-content/plugins/[boombox-folder]/index.php for the 'Version' field.
    Affected if The version number is 1.8.0 or lower (vulnerable versions are up to and including 1.8.0)
  3. Verify if the plugin is active
    In WordPress admin > Plugins, check if BoomBox Theme Extensions shows 'Active' status. If inactive, the shortcode vulnerability cannot be exploited.
    Affected if The plugin status is Active (inactive plugins cannot be exploited through shortcodes)
  4. Check for contributor-level or higher user accounts
    In WordPress admin > Users, review the user list. Look for any users with the 'Contributor', 'Author', 'Editor', or 'Administrator' role. Contributor-level permission is sufficient to exploit this vulnerability.
    Affected if At least one user account has Contributor role or higher permissions

You are affected if BoomBox Theme Extensions plugin version 1.8.0 or lower is installed and active, and any user with Contributor-level access or higher exists in the WordPress environment.

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 BoomBox Theme Extensions plugin to version 1.8.1 or later. If no update is available, disable the plugin immediately and review server logs for signs of exploitation.

Recommended fix Moderate confidence

Version greater than 1.8.0 (check WordPress plugin repository for latest available version)

  1. 1. Verify the current version of the BoomBox Theme Extensions plugin installed on the WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. If a version newer than 1.8.0 is available, click 'Update Now' to install the patched version
  4. 4. If no update is available, consider temporarily disabling the plugin until a patched version is released
  5. 5. Alternatively, restrict contributor-level permissions pending the security update

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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