dbcve.org
Siteorigin Widgets BundleWordPress extension · Siteorigin

CVE-2024-5901

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-30
Fix available
A fix is available. Upgrade to 1.62.3 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 SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Image Grid widget in all versions up to, and including, 1.62.2 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 SiteOrigin Widgets Bundle WordPress plugin contains a stored XSS vulnerability in its Image Grid widget. Due to insufficient input sanitization and output escaping on user-supplied attributes, authenticated users with contributor-level access or higher can inject arbitrary JavaScript that persists on pages and executes when other users access those pages.

MitigationUpdate the SiteOrigin Widgets Bundle plugin to version 1.62.3 or later to address the improper input sanitization and output escaping in the Image Grid widget.

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
Siteorigin Widgets BundleWordPress extension
Affected:< 1.62.3

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 SiteOrigin Widgets Bundle plugin installation and version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate 'SiteOrigin Widgets Bundle', or use WP-CLI: wp plugin list --name='siteorigin-widgets-bundle' --format=table
    Affected if Plugin is installed and version is below 1.62.3
  2. Identify pages or posts using the Image Grid widget
    Search your WordPress database for posts containing the 'sow-image-grid' shortcode or widget, or check page builder layouts that include the Image Grid widget. In WP-CLI: wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%sow-image-grid%' AND post_status='publish'"
    Affected if Any published content contains the Image Grid widget from this plugin
  3. Inspect Image Grid widget attributes for unsanitized input
    Edit a page/post containing the Image Grid widget and examine the widget fields (such as image URLs, titles, or links). Check the page source of the rendered front-end content to see if these attributes are properly escaped (look for &lt;script&gt; tags or unescaped quote characters in HTML attributes)
    Affected if Widget attributes contain unsanitized user input that appears as raw HTML in the page source (not properly escaped)
  4. Review user role permissions for widget access
    Go to WordPress Admin > Users > Roles or use a role management plugin to check which roles have permission to edit widgets or use the SiteOrigin Page Builder. Contributor-level and above users can exploit this vulnerability.
    Affected if Users with contributor-level access or higher can edit content containing the Image Grid widget

You are affected if the SiteOrigin Widgets Bundle plugin version is below 1.62.3 AND the Image Grid widget is in use on your site, allowing authenticated users with contributor+ roles to inject stored XSS.

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.62.3 or later
Fixed in 1.62.3
Interim mitigation

Update the SiteOrigin Widgets Bundle plugin to version 1.62.3 or later to address the improper input sanitization and output escaping in the Image Grid widget.

Recommended fix High confidence

1.62.3 or higher

  1. 1. Back up your WordPress site before making any changes
  2. 2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. 3. Find the SiteOrigin Widgets Bundle plugin
  4. 4. Click Update Now to install the latest version (1.62.3 or higher)
  5. 5. Alternatively, you can update automatically via WordPress > Dashboard > Updates
  6. 6. After updating, verify the plugin version shows 1.62.3 or higher in the plugins list

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

Fix this in Siteorigin Widgets Bundle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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