The Plus Addons For ElementorWordPress extension · Posimyth
CVE-2024-3197
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 The Plus Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom attributes in the plugin's widgets in all versions up to, and including, 5.4.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 confidenceThe Plus Addons for Elementor plugin for WordPress contains a stored XSS vulnerability in versions up to 5.4.2. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through custom widget attributes due to insufficient input sanitization and output escaping. The malicious scripts execute 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
The Plus Addons For ElementorWordPress extension
< 5.5.0CVSS 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 the plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/the-plus-addons-for-elementor directory exists on the serverAffected if The Plus Addons for Elementor plugin is present in the WordPress installation
-
Check the installed versionIn WordPress admin, go to Plugins > Installed Plugins and locate The Plus Addons For Elementor to see the version number, or read the main plugin file headerAffected if The version number displayed is less than 5.5.0 (for example, 5.4.2 or earlier)
-
Identify custom widget usageEdit pages or posts using Elementor and examine any widgets that have custom attributes or custom CSS/JS fields added through the pluginAffected if Custom attributes, custom code fields, or custom JS fields are present in any widget on the site
-
Inspect page source for injected scriptsView the source code of pages using the plugin widgets and search for <script tags or javascript: URIs within widget attribute valuesAffected if Unexpected script tags, event handlers, or javascript: links appear in HTML attributes of plugin widgets
-
Review recent contributor-level user activityCheck WordPress user roles and audit recent posts or pages created by users with contributor or author roles for suspicious content in widget settingsAffected if Contributor-level users have created or edited content with the plugin since the vulnerability was disclosed
A user is affected if the plugin version is below 5.5.0 AND custom widget attributes are being used on published pages, allowing stored XSS to execute for visitors.
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 · scoped5.5.0
Update the plugin to version 5.4.3 or later to patch the vulnerability, and audit existing content for any injected malicious scripts.
The Plus Addons for Elementor version 5.5.0 or later
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find 'The Plus Addons for Elementor' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 5.5.0 or later
- Verify the update completed successfully
- Test that affected widgets function correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in The Plus Addons For Elementor
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3197 — 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-3197 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