dbcve.org
Boot StoreWordPress extension · Thecartpress

CVE-2024-5938

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to after 1.6.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Boot Store theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘link’ parameter within the theme's Button shortcode in all versions up to, and including, 1.6.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Boot Store WordPress theme has a stored XSS vulnerability in its Button shortcode's 'link' parameter. Attackers with Contributor-level permissions can inject malicious JavaScript through the unsanitized link parameter, which executes when other users view pages containing the injected shortcode.

MitigationUpdate Boot Store theme to version 1.6.5 or later, which implements proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_url) for the link parameter.

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
Boot StoreWordPress extension
Affected:<= 1.6.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Check Boot Store theme version
    Navigate to Appearance > Themes in WordPress admin. Locate the Boot Store theme (by Thecartpress) and view its details to find the installed version number. Alternatively, check the style.css file in the theme directory for the 'Version:' header.
    Affected if The installed version is 1.6.4 or lower.
  2. Identify Button shortcode usage
    Search your WordPress database for instances of the 'button' shortcode. This can be done via phpMyAdmin by querying the wp_posts table for content containing '[button' or by using a plugin that searches post content. Also check widget areas if they support shortcodes.
    Affected if Any page, post, or custom post type contains a Button shortcode with a link parameter.
  3. Inspect shortcode link parameter values
    Examine the link parameter in any found Button shortcodes. Look for values that contain JavaScript: URLs, event handlers (onclick, onload, etc.), or suspicious encoded content. View the raw post content or use a shortcode viewer plugin to see exact parameter values.
    Affected if The link parameter contains unsanitized user-supplied URLs or JavaScript code (e.g., javascript:alert(1)).
  4. Review recent contributor-level users
    Check Users > All Users in WordPress admin for any accounts with Contributor role. Review their recent posts for Button shortcodes with external link parameters that may contain malicious scripts.
    Affected if A Contributor-level user account exists and has published content containing Button shortcodes.

You are affected if the Boot Store theme version is 1.6.4 or lower AND any Button shortcode with a link parameter exists in your content, regardless of whether malicious payload is currently visible.

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 a release after 1.6.4
Interim mitigation

Update Boot Store theme to version 1.6.5 or later, which implements proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_url) for the link parameter.

Recommended fix Moderate confidence

Latest version available on WordPress.org theme repository (version > 1.6.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Boot Store theme
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the official WordPress theme repository (themes.trac.wordpress.org) and upload it via Appearance > Themes > Add New > Upload Theme
  6. 6. After updating, verify the theme version is greater than 1.6.4
  7. 7. Test the Button shortcode functionality to ensure the fix works correctly

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

Fix this in Boot Store 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 the upgrade done

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