CVE-2024-2121
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 Elementor Website Builder Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Media Carousel widget in all versions up to, and including, 3.20.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions 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 Elementor Website Builder Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting in the Media Carousel widget. Authenticated attackers with contributor-level or higher permissions can inject malicious JavaScript through unsanitized user-supplied attributes in the widget. The injected scripts persist and execute whenever users access the compromised 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< 3.20.2CVSS 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.
-
Verify Elementor Pro is installedGo to WordPress dashboard > Plugins and check if 'Elementor Website Builder Pro' appears in the installed plugins listAffected if Elementor Pro is not installed
-
Check the installed Elementor Pro versionNavigate to WordPress dashboard > Plugins > Installed Plugins > Elementor Website Builder Pro and compare the version number to 3.20.2Affected if The installed version is lower than 3.20.2
-
Inspect pages using the Media Carousel widgetOpen the WordPress editor (Elementor) and search for pages containing the Media Carousel widget, or inspect the site pages directly if you cannot access the editorAffected if Any page uses the Media Carousel widget on a site with vulnerable Elementor Pro
-
Review Media Carousel widget attributes for suspicious script contentEdit each page with the Media Carousel widget in Elementor, select the widget, and examine fields such as Image, Title, Description, and Custom Link for unexpected characters like <script>, javascript:, or event handlers like onload/onerrorAffected if Any Media Carousel widget contains unsanitized user-supplied attributes with malicious script payloads
You are affected if Elementor Website Builder Pro version is below 3.20.2 AND any page on your site uses the Media Carousel widget with potentially malicious injected attributes
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 · scoped3.20.2
Update Elementor Website Builder Pro to version 3.20.2 or later which includes proper input sanitization and output escaping. Until patched, review pages using the Media Carousel widget for suspicious content and consider limiting contributor-level publishing capabilities.
Elementor Pro 3.20.2
- 1. Create a full backup of your WordPress site (database and files) before proceeding with any updates.
- 2. Navigate to WordPress Dashboard > Plugins.
- 3. Locate Elementor Pro in the plugins list.
- 4. If an update is available, click 'Update Now' to update Elementor Pro to version 3.20.2 or later.
- 5. Alternatively, go to Dashboard > Updates to check for and apply the update.
- 6. After updating, verify the fix by confirming the Media Carousel widget now properly sanitizes and escapes user-supplied attributes.
- 7. Test that the Media Carousel widget functions correctly with various media types.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2121 — 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-2121 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