dbcve.org
ShopbuilderWordPress extension · Radiustheme

CVE-2024-37520

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 2.1.13 or later.
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme ShopBuilder – Elementor WooCommerce Builder Addons shopbuilder.This issue affects ShopBuilder – Elementor WooCommerce Builder Addons: from n/a through <= 2.1.12.

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

A Remote File Inclusion (RFI) vulnerability in the RadiusTheme ShopBuilder WordPress plugin allows attackers to include external malicious files via unsanitized user input in PHP include/require statements. This can lead to arbitrary code execution on the server.

MitigationUpgrade to a patched version of ShopBuilder (contact vendor for latest version), or implement web application firewall (WAF) rules to block directory traversal and remote URL inclusion attempts until patch is available.

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
ShopbuilderWordPress extension
Affected:< 2.1.13

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. Confirm ShopBuilder plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'shopbuilder' or similar Radiustheme ShopBuilder plugin directory
    Affected if The ShopBuilder plugin by Radiustheme is present in the WordPress installation
  2. Identify the installed ShopBuilder version
    Check the plugin's main PHP file header for 'Version:' comment, or check the plugin's readme.txt file, or view the plugin details in WordPress admin Plugins page
    Affected if The version number found is less than 2.1.13 (e.g., 2.1.12, 2.1.10, etc.) or if no version is displayed and the plugin is present
  3. Verify the vulnerable RFI code path exists
    If possible, inspect the plugin PHP files for include/require statements that use user-supplied parameters (e.g., $_GET, $_POST) without proper sanitization, particularly in files that handle template or file inclusion
    Affected if The plugin code contains unsanitized user input being used in include(), require(), include_once(), or require_once() functions

A WordPress site is affected if the RadiusTheme ShopBuilder plugin is installed with a version lower than 2.1.13, as this version range contains the RFI vulnerability in unsanitized PHP include/require statements.

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.1.13 or later
Fixed in 2.1.13
Interim mitigation

Upgrade to a patched version of ShopBuilder (contact vendor for latest version), or implement web application firewall (WAF) rules to block directory traversal and remote URL inclusion attempts until patch is available.

Recommended fix High confidence

2.1.13 or later

  1. 1. Create a full backup of your WordPress site and database before updating.
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find the ShopBuilder – Elementor WooCommerce Builder Addons plugin.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.1.13 or later.
  5. 5. Verify the update completed successfully by checking the plugin version.
  6. 6. Test critical e-commerce functionality (product pages, cart, checkout) to ensure the update did not break any features.

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

Fix this in Shopbuilder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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