dbcve.org
Elementor Page BuilderWordPress extension · Elementor

CVE-2025-3076

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 3.29.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
The Elementor Website Builder Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘button_text’ parameter in all versions up to, and including, 3.29.0 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 confidence

The Elementor Website Builder Pro WordPress plugin fails to properly sanitize and escape the 'button_text' parameter, allowing authenticated users with Contributor-level access or higher to inject malicious JavaScript code. This stored XSS executes whenever other users access pages containing the compromised button element.

MitigationUpdate Elementor Website Builder Pro to version 3.29.1 or later. If immediate patching is not possible, restrict contributor-level user permissions or disable the affected button functionality until the update can be applied.

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
Elementor Page BuilderWordPress extension
Affected:< 3.29.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 Elementor Page Builder version
    Navigate to WordPress Dashboard > Plugins > Installed Plugins > Elementor Page Builder and check the version number displayed, or use WP-CLI: wp plugin list --name=elementor
    Affected if The installed version is lower than 3.29.1
  2. Identify Contributor-level users
    Go to WordPress Dashboard > Users and review user roles, or use WP-CLI: wp user list --role=contributor
    Affected if Any user account with Contributor-level permissions exists on the site
  3. Inspect button elements in pages/posts
    Review pages and posts created with Elementor that contain button widgets. Check the 'Button Text' field in the Elementor editor for each button element, or inspect the page HTML for unusual script injections in button tags
    Affected if A button element contains unsanitized or injected script code in its text content
  4. Check for stored XSS in button_text
    View the source code of published Elementor pages containing buttons. Look for unescaped characters or script tags within button text attributes or content, or use database query: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%button_text%' and examine values for suspicious patterns
    Affected if The button_text parameter contains raw HTML or script tags without proper escaping

A user is affected if Elementor Page Builder version is below 3.29.1 and pages exist containing button elements editable by Contributor-level users, as the unsanitized button_text parameter could contain injected malicious scripts.

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

Update Elementor Website Builder Pro to version 3.29.1 or later. If immediate patching is not possible, restrict contributor-level user permissions or disable the affected button functionality until the update can be applied.

Recommended fix High confidence

Elementor Page Builder Pro version 3.29.1

  1. Create a full backup of the WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Elementor Page Builder Pro
  3. Update Elementor Page Builder Pro to version 3.29.1 or later
  4. Verify the update completed successfully by checking the installed version number
  5. Test that the button_text functionality works correctly after the update
  6. Clear any caching plugins or server-side caches if applicable

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

Fix this in Elementor Page Builder Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
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,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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