dbcve.org
Pricing TablesWordPress extension · Webdevocean

CVE-2024-13582

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 1.0 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 Simple Pricing Tables For WPBakery Page Builder(Formerly Visual Composer) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wdo_simple_pricing_table_free' shortcode in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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 Simple Pricing Tables For WPBakery Page Builder WordPress plugin is vulnerable to stored Cross-Site Scripting (XSS) via the 'wdo_simple_pricing_table_free' shortcode. The vulnerability exists because user-supplied attributes in the shortcode are not properly sanitized before output, allowing authenticated attackers with contributor-level access or higher to inject malicious JavaScript that executes when other users view affected pages.

MitigationUpdate the plugin to a patched version once available, or remove/quarantine the plugin until a fix is released. Audit existing pages using the shortcode to identify and remove any injected malicious scripts.

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
Pricing TablesWordPress extension
Affected:<= 1.0

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. Identify if the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Simple Pricing Tables For WPBakery Page Builder' or 'Webdevocean Pricing Tables'. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to 'simple-pricing-tables-for-wpbakery' or 'webdevocean-pricing-tables'.
    Affected if The plugin is present on the WordPress site.
  2. Check the installed plugin version
    In WordPress admin > Plugins, find the plugin and look at the version number displayed. Compare it to the affected range: version 1.0 and below.
    Affected if The installed version is 1.0 or lower.
  3. Detect usage of the vulnerable shortcode
    Search the WordPress database for the shortcode 'wdo_simple_pricing_table_free'. This can be done via phpMyAdmin with query: SELECT * FROM wp_posts WHERE post_content LIKE '%wdo_simple_pricing_table_free%' (wp_ prefix may vary). Alternatively, search theme files and page content manually.
    Affected if Pages or posts containing the shortcode exist on the site.
  4. Inspect shortcode attributes for unsanitized output
    Review the content of pages/posts using the shortcode. Check the shortcode attributes in the post_content field for any unusual characters, script tags, or event handlers (onclick, onerror, onload, etc.) that may indicate injected XSS payloads.
    Affected if The shortcode contains unexpected attributes with JavaScript code or HTML tags.
  5. Verify user account roles
    In WordPress admin > Users, review the list of user accounts. Identify any users with Contributor, Author, Editor, or Administrator roles since these roles can use the shortcode.
    Affected if There are users with Contributor-level access or higher who could have authored content with the vulnerable shortcode.

A site is affected if it has Webdevocean Pricing Tables (Simple Pricing Tables For WPBakery Page Builder) version 1.0 or lower installed AND has pages or posts using the wdo_simple_pricing_table_free shortcode.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Update the plugin to a patched version once available, or remove/quarantine the plugin until a fix is released. Audit existing pages using the shortcode to identify and remove any injected malicious scripts.

Fix this in Pricing Tables 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-13582 — 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-13582 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