dbcve.org
Primary Addon For ElementorWordPress extension · Nicheaddons

CVE-2024-54314

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 1.6.2 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.6.0.

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

A Stored XSS vulnerability exists in the Primary Addon for Elementor plugin (versions through 1.6.0) where user-supplied input is not properly sanitized or escaped before being rendered in web pages, allowing malicious JavaScript to be stored and executed when other users view the affected content.

MitigationUpdate the Primary Addon for Elementor plugin to the latest version once available, which should include proper input sanitization and output encoding. If no update exists, implement WordPress sanitization functions (such as esc_html(), esc_attr(), and wp_kses()) on all user input before output.

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.6.2

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 and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Nicheaddons Primary Addon For Elementor'. Check the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header or version.php for the 'Version' constant.
    Affected if The installed version is below 1.6.2 (versions 1.6.0 and earlier are confirmed affected)
  2. Verify Elementor page builder is active
    Check if the Elementor website builder plugin is installed and active in the WordPress environment. This vulnerability exists in the Elementor addon, so Elementor must be present for the attack surface to exist.
    Affected if Elementor is installed and active, creating the conditions for the vulnerable addon to function
  3. Identify plugin widgets with user input
    In Elementor editor, review available widgets provided by Primary Addon for Elementor. Focus on widgets that accept user input such as forms, contact fields, login/registration widgets, search widgets, or any widget that displays user-submitted content.
    Affected if Any Primary Addon widgets that accept or display user input are in use on the site
  4. Inspect form submissions for stored content
    Check WordPress admin for any submitted forms, user registrations, or content created by visitors using the plugin's widgets. Look in the database tables for submitted data that might contain unsanitized HTML or JavaScript.
    Affected if Form submissions or user-generated content exists in the database that could contain malicious scripts
  5. Review page source for unescaped output
    View the source code of pages containing Primary Addon widgets. Search for user input values that appear in HTML attributes or content without proper encoding (look for unescaped quotes, <script> tags, or event handlers like onload/onerror).
    Affected if User-supplied data appears in the HTML output without proper sanitization (e.g., raw quotes, unencoded special characters)

You are affected if the Primary Addon for Elementor plugin version is below 1.6.2 AND Elementor is active AND any plugin widgets that accept user input are in use on your site.

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.6.2 or later
Fixed in 1.6.2
Interim mitigation

Update the Primary Addon for Elementor plugin to the latest version once available, which should include proper input sanitization and output encoding. If no update exists, implement WordPress sanitization functions (such as esc_html(), esc_attr(), and wp_kses()) on all user input before output.

Recommended fix Moderate confidence

1.6.2

  1. Update Primary Addon for Elementor plugin to version 1.6.2 or later through your WordPress plugin management interface
  2. After updating, verify the plugin version shows 1.6.2 or higher in the installed 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
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

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