dbcve.org
Astra WidgetsWordPress extension · Brainstormforce

CVE-2024-50439

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 1.2.15 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 Brainstorm Force Astra Widgets astra-widgets allows Stored XSS.This issue affects Astra Widgets: from n/a through <= 1.2.14.

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

Stored XSS vulnerability in Brainstorm Force Astra Widgets allows attackers to inject malicious JavaScript through widget input fields. The unsanitized input is stored in the database and executed when users view pages containing the affected widgets.

MitigationUpdate to the latest version of Astra Widgets. Until a patch is available, implement proper input sanitization using WordPress escaping functions (such as esc_html(), esc_attr(), or sanitize_text_field()) on all widget output, and consider input validation on widget form submissions.

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
Astra WidgetsWordPress extension
Affected:< 1.2.15

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 Astra Widgets plugin version
    Log into WordPress admin, go to Plugins > Installed Plugins, locate 'Astra Widgets' or 'Astra Sites & Widgets' by Brainstorm Force, and note the version number displayed
    Affected if The installed version is lower than 1.2.15
  2. Identify active Astra widgets on the site
    Go to Appearance > Widgets in WordPress admin, or check page builders (Elementor/Beaver Builder) if Astra widgets are used in layouts. Document which widget types are in use
    Affected if Any Astra widgets are active on the site and the version is vulnerable
  3. Inspect widget input data for suspicious content
    Access the WordPress database (via phpMyAdmin or wp-cli), examine tables storing widget data (typically wp_options with option_name containing 'widget_', or custom postmeta tables), and look for unsanitized script tags, javascript: URIs, or event handlers in widget content fields
    Affected if Widget data contains raw script tags, onload/onerror attributes, or javascript: protocols without sanitization
  4. View page source of widget-enabled pages
    Visit pages containing Astra widgets, right-click > View Page Source, and search for widget output areas. Look for unescaped HTML, script tags, or event handlers in the rendered markup
    Affected if Widget output displays raw HTML or script content instead of escaped text

You are affected if Astra Widgets version is below 1.2.15 AND any Astra widgets with user-editable input fields are active on your site.

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.2.15 or later
Fixed in 1.2.15
Interim mitigation

Update to the latest version of Astra Widgets. Until a patch is available, implement proper input sanitization using WordPress escaping functions (such as esc_html(), esc_attr(), or sanitize_text_field()) on all widget output, and consider input validation on widget form submissions.

Recommended fix High confidence

Astra Widgets version 1.2.15

  1. 1. Back up your WordPress site database and files before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. 3. Locate the 'Astra Widgets' plugin in the list
  4. 4. Click 'Update now' if an update is available, or manually upload version 1.2.15
  5. 5. After updating, verify the plugin shows version 1.2.15 in the plugins list
  6. 6. Clear any caching plugins or server-side caches
  7. 7. Test that the Astra Widgets functionality works correctly on your site

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

Fix this in Astra Widgets Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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