dbcve.org
Primary Addon For ElementorWordPress extension · Nicheaddons

CVE-2024-44033

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to 1.5.8 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 nicheaddons Primary Addon for Elementor primary-addon-for-elementor allows Stored XSS.This issue affects Primary Addon for Elementor: from n/a through <= 1.5.7.

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

Stored Cross-site Scripting (XSS) vulnerability in the Primary Addon for Elementor WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized user inputs. The script is stored in the database and executes when other users view pages containing the compromised content, potentially leading to session hijacking or privilege escalation.

MitigationUpdate Primary Addon for Elementor to the latest patched version beyond 1.5.7. If no update is available, disable the plugin until a fix is released. Review existing content for injected malicious scripts.

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
Primary Addon For ElementorWordPress extension
Affected:< 1.5.8

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 installation
    Navigate to WordPress admin dashboard > Plugins and locate 'Primary Addon for Elementor' or 'Nicheaddons Primary Addon For Elementor' in the installed plugins list. Alternatively, check if the directory /wp-content/plugins/niche-addons-for-elementor/ exists on the server.
    Affected if The plugin is installed and active
  2. Check installed version
    In WordPress admin > Plugins, click 'View Details' on Primary Addon for Elementor to display the version number. Compare against the vulnerable range: any version below 1.5.8 is affected.
    Affected if Installed version is lower than 1.5.8
  3. Identify Elementor content usage
    Query the WordPress database: SELECT COUNT(*) FROM wp_posts WHERE post_content LIKE '%elementor%' OR post_type IN ('elementor_library', 'page', 'post'); This identifies posts/pages created or edited with Elementor that may contain the vulnerable widget.
    Affected if The site uses Elementor to create or edit content and the vulnerable plugin version is installed
  4. Scan for injected scripts in database
    Search wp_posts table for script tags or JavaScript event handlers in post_content: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%onload=%'; Also check wp_postmeta for malicious values in meta_key fields.
    Affected if Suspicious script tags or event handlers are found in post content or postmeta values that were created/modified after the plugin was installed

A user is affected if the Primary Addon for Elementor plugin is installed with a version below 1.5.8 AND the site uses Elementor to create content, as this creates the attack surface for stored XSS injection.

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

Update Primary Addon for Elementor to the latest patched version beyond 1.5.7. If no update is available, disable the plugin until a fix is released. Review existing content for injected malicious scripts.

Recommended fix High confidence

1.5.8

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Primary Addon for Elementor' by nicheaddons
  4. Click 'Update Now' to install version 1.5.8 or later, or manually upload the updated plugin package if automatic updates are not enabled
  5. After updating, verify the new version is 1.5.8 or higher in the plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Primary Addon For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Check whether your project pulls in CVE-2024-44033 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-44033 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