dbcve.org
Web Stories Widgets For ElementorWordPress extension · Coolplugins

CVE-2024-52354

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-11
Fix available
A fix is available. Upgrade to 1.1.1 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Cool Plugins Web Stories Widgets For Elementor shortcodes-for-amp-web-stories-and-elementor-widget allows Stored XSS.This issue affects Web Stories Widgets For Elementor: from n/a through <= 1.1.

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 · moderate confidence

This is a Stored XSS vulnerability in the 'Web Stories Widgets For Elementor' WordPress plugin. The plugin's shortcode functionality fails to properly sanitize user-supplied input before rendering it in web pages, allowing attackers to inject malicious JavaScript that executes whenever visitors view affected pages.

MitigationUpdate to the latest version of Web Stories Widgets For Elementor. If no update is available, disable the plugin or implement content security policy headers to mitigate XSS execution.

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
Web Stories Widgets For ElementorWordPress extension
Affected:< 1.1.1

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. Verify the plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the wp-content/plugins directory for a folder containing 'web-stories' or 'web-stories-widgets'
    Affected if The plugin 'Web Stories Widgets For Elementor' appears in the installed plugins list
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for 'Web Stories Widgets For Elementor', or inspect the main plugin file (usually named plugin-name.php) and look for the 'Version' header comment
    Affected if The version number is lower than 1.1.1 (e.g., 1.1.0, 1.0.x, etc.)
  3. Identify shortcode usage
    Search WordPress database via phpMyAdmin or WP CLI for instances of the plugin's shortcode (typically [web_stories_widget] or similar) in the wp_posts table, or check pages/posts in the WordPress editor for the Web Stories widget
    Affected if The shortcode or widget is present and being used on any published page or post
  4. Inspect rendered output for unsanitized content
    View a page containing the Web Stories shortcode/widget in a browser, right-click and view page source, then search for the story content area; check if user-supplied text appears without proper HTML encoding (look for unescaped quotes, script tags, or HTML attributes)
    Affected if Raw user input appears unescaped in the HTML output, indicating lack of sanitization

You are affected if the plugin version is below 1.1.1 AND the Web Stories widget/shortcode is actively used on your site, allowing stored XSS to execute when visitors view those pages.

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 1.1.1 or later
Fixed in 1.1.1
Interim mitigation

Update to the latest version of Web Stories Widgets For Elementor. If no update is available, disable the plugin or implement content security policy headers to mitigate XSS execution.

Recommended fix High confidence

Web Stories Widgets For Elementor version 1.1.1

  1. Backup your WordPress site database and files
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Find 'Web Stories Widgets For Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.1.1 from the WordPress repository
  5. Verify the plugin version is 1.1.1 after updating
  6. Test the affected functionality to confirm the XSS vulnerability is remediated

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

Fix this in Web Stories Widgets For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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