The Plus Addons For ElementorWordPress extension · Posimyth

CVE-2024-35709

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 5.5.5 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
Improper 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.This issue affects The Plus Addons for Elementor Page Builder Lite: from n/a through <= 5.5.4.

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 · moderate confidence

This is a stored Cross-site Scripting (XSS) vulnerability in The Plus Addons for Elementor Page Builder Lite plugin. The vulnerability allows authenticated attackers to inject malicious JavaScript code through plugin settings or widget inputs that are not properly sanitized, which then executes when other users view affected pages in the Elementor page builder.

MitigationUpdate The Plus Addons for Elementor Page Builder Lite to the latest version beyond 5.5.4. If immediate updating is not possible, restrict editor-level access to trusted users only and implement additional input sanitization at the web application firewall level.

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
Affected:< 5.5.5

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. Confirm plugin presence
    In WordPress admin, go to Plugins and verify 'The Plus Addons for Elementor' by Posimyth is installed and activated
    Affected if Plugin is present and active in the WordPress site
  2. Identify installed version
    Access the Plugins page in WordPress admin, locate The Plus Addons for Elementor, and record the version number displayed
    Affected if Version is earlier than 5.5.5
  3. Review user access levels
    Navigate to WordPress Users section and check which roles have access to Elementor page builder editing capabilities
    Affected if Users with editor or contributor roles who are not fully trusted can access the Elementor editor

The environment is affected if The Plus Addons for Elementor is installed with a version lower than 5.5.5 and untrusted users have access to edit pages with Elementor

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

Update The Plus Addons for Elementor Page Builder Lite to the latest version beyond 5.5.4. If immediate updating is not possible, restrict editor-level access to trusted users only and implement additional input sanitization at the web application firewall level.

Recommended fix High confidence

5.5.5

  1. Create a complete backup of your WordPress site before updating
  2. Navigate to WordPress Dashboard > Plugins > Installed Plugins
  3. Locate 'The Plus Addons for Elementor Page Builder Lite' in the plugin list
  4. Click 'Update now' when an update to version 5.5.5 or higher is available, or manually upload version 5.5.5
  5. After updating, clear any caching mechanisms (site cache, CDN cache, browser cache)
  6. Verify the plugin shows version 5.5.5 or higher as active
Caveat Routine plugin update; test in staging environment before deploying to production as a best practice

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
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35709 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35709 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