CVE-2024-43977
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in POSIMYTH The Plus Addons for Elementor Page Builder Lite the-plus-addons-for-elementor-page-builder allows Stored XSS.This issue affects The Plus Addons for Elementor Page Builder Lite: from n/a through <= 5.6.2.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in The Plus Addons for Elementor Page Builder Lite plugin allows authenticated attackers to inject malicious JavaScript through plugin components that fail to properly sanitize user input. The malicious script executes when other users view pages containing the injected payload.
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.6.3CVSS 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 the plugin is installedIn WordPress admin, go to Plugins and verify 'The Plus Addons for Elementor' or 'The Plus Addons for Elementor Page Builder Lite' is present and activatedAffected if The plugin is installed and active in WordPress
-
Check the installed version numberIn the Plugins list, locate the plugin and read the version number displayed beneath the plugin nameAffected if The version is below 5.6.3 (versions 5.6.2 and earlier are affected)
-
Identify active Plus Addons componentsReview your published pages and posts created with Elementor. Look for any widgets or elements from The Plus Addons plugin (often labeled with tp- or The Plus) in the page contentAffected if Pages or posts contain active Plus Addons widgets or elements that accept user input
-
Inspect for injected scripts in plugin component fieldsEdit pages containing Plus Addons elements and examine text input fields (such as heading text, button labels, content fields, or custom CSS/JS fields). View the page source or use browser developer tools to check for unexpected script tags or event handlers like onload, onerror, or javascript:Affected if Malicious script payloads are found stored in Plus Addons input fields
The environment is affected if the plugin version is below 5.6.3 and any Plus Addons components with user input fields are in use on published pages.
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.6.3
Update the plugin to the latest version beyond 5.6.2 when available, or disable the plugin until a patch is released. Audit existing pages and posts using the affected plugin components for any injected malicious scripts.
The Plus Addons for Elementor version 5.6.3
- 1. Create a full backup of your WordPress site (database and files) before making any changes
- 2. Log in to your WordPress admin dashboard
- 3. Navigate to Plugins > Installed Plugins
- 4. Find 'The Plus Addons for Elementor' in the plugin list
- 5. If an update is available, click 'Update Now' to upgrade to version 5.6.3
- 6. Alternatively, you can update via WordPress admin > Dashboard > Updates, or use a plugin manager like WP-CLI: wp plugin update the-plus-addons-for-elementor-page-builder
- 7. After updating, verify the plugin version shows 5.6.3
- 8. Clear any caching plugins or server-side caches to ensure the patched code is served
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43977 — 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-43977 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