CVE-2024-5341
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 Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'size' attribute of the Heading Title widget in all versions up to, and including, 5.5.4 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 versions up to 5.5.4 contain a stored XSS vulnerability in the Heading Title widget's 'size' attribute. Authenticated attackers with contributor-level access can inject malicious JavaScript via insufficiently sanitized input, which persists in the database and executes when other 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< 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.
-
Confirm plugin installation and versionNavigate to WordPress dashboard > Plugins and locate 'Posimyth The Plus Addons For Elementor'. Note the installed version number displayed in the plugin list.Affected if The installed version is earlier than 5.5.0 (e.g., 5.4.9, 5.4.0, etc.)
-
Verify Heading Title widget usageIn Elementor editor, search for 'Heading Title' widget in the widget panel. Check any pages/posts where this widget has been added to the layout.Affected if The Heading Title widget is present and actively used on any published page or post in the site.
-
Inspect size attribute in databaseAccess the WordPress database via phpMyAdmin or command line. Query the postmeta table for entries matching the Heading Title widget settings. Look for the 'size' parameter in the meta_value field.Affected if The 'size' attribute contains unsanitized HTML or JavaScript (e.g., <script> tags, event handlers like onload/onerror, or javascript: URIs).
-
Review user access levelsCheck WordPress user roles for any accounts with contributor-level access. Review published content created by these users that include the Heading Title widget.Affected if Contributor-level users exist and have created or edited pages containing the Heading Title widget.
You are affected if the Plus Addons for Elementor plugin version is below 5.5.0 AND the Heading Title widget is in use on your site, as the XSS payload would be stored in the 'size' attribute database entry.
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.5.5 or later. If patching is not immediately possible, implement proper input sanitization (such as sanitize_text_field) and output escaping (such as esc_attr) on the 'size' attribute in the Heading Title widget code.
5.5.5 or later (latest stable release)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'The Plus Addons for Elementor' in the plugin list
- Check if the current version is below 5.5.5 (versions 5.5.4 and below are affected by this XSS vulnerability)
- If vulnerable, click 'Update now' to update to the latest version, or manually download the latest version from wordpress.org and upload it
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5341 — 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-5341 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