Page BuilderWordPress extension · Siteorigin
CVE-2024-2202
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 · uneditedThe Page Builder by SiteOrigin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the legacy Image widget in all versions up to, and including, 2.29.6 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 confidenceThe Page Builder by SiteOrigin WordPress plugin up to version 2.29.6 contains a stored XSS vulnerability in its legacy Image widget due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level permissions can inject malicious JavaScript that executes whenever users access affected pages.
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
Page BuilderWordPress extension
< 2.29.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Page Builder versionIn WordPress admin, go to Plugins > Installed Plugins, locate 'Page Builder by SiteOrigin', and note the version number displayed.Affected if The installed version is lower than 2.29.7 (e.g., 2.29.6 or earlier).
-
Identify legacy Image widget usageNavigate to Pages or Posts in the WordPress admin, edit any page, and inspect the page builder interface to see if the legacy Image widget has been added to any page layouts.Affected if The legacy Image widget from Page Builder appears in any published or draft page/post content.
-
Review page content for injected scriptsView the source code of pages using the Image widget, or use the browser developer tools to inspect image elements for unexpected attributes such as onmouseover, onerror, or javascript: URIs within alt text or title fields.Affected if Malicious JavaScript code (such as event handlers like onmouseover) is present in image-related attributes in the HTML output.
A user is affected if their SiteOrigin Page Builder plugin version is below 2.29.7 AND any page uses the legacy Image widget with potentially malicious content injected by a contributor-level user.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.29.7
Update the Page Builder by SiteOrigin plugin to version 2.29.7 or later. Until then, restrict contributor-level user creation and review existing pages using the legacy Image widget for suspicious content.
Page Builder by SiteOrigin version 2.29.7
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Page Builder by SiteOrigin' in the plugin list
- Check if the current version is below 2.29.7
- If vulnerable, click 'Update Now' to upgrade to the latest version
- After update, verify the version number shows 2.29.7 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Page Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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