Sales Page AddonWordPress extension · Nicheaddons
CVE-2024-51585
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 nicheaddons Sales Page Addon – Elementor & Beaver Builder sales-page-addon allows Stored XSS.This issue affects Sales Page Addon – Elementor & Beaver Builder: from n/a through <= 1.4.5.
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 confidenceThis is a Stored Cross-Site Scripting (XSS) vulnerability in the Sales Page Addon plugin for Elementor and Beaver Builder. The plugin fails to properly sanitize and escape user input before rendering it in web pages, allowing attackers to inject malicious JavaScript code that persists on the server and executes when other users view the affected content.
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
Sales Page AddonWordPress extension
<= 1.4.2CVSS 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.
-
Check if Nicheaddons Sales Page Addon plugin is installedNavigate to WordPress admin > Plugins, or check for the plugin directory at wp-content/plugins/nicheaddons-sales-page/Affected if The plugin directory does not exist - you are not affected.
-
Determine the installed plugin versionOpen the main plugin file (usually nicheaddons-sales-page.php) and locate the version in the plugin header comment, or view the plugin in WordPress admin plugins list which displays the version numberAffected if The displayed version is 1.4.2 or lower - the vulnerable version is installed.
-
Verify the plugin is activeCheck WordPress admin > Plugins > Active Plugins list, or check the wp_options table for the active_plugins option to confirm nicheaddons-sales-page is enabledAffected if The plugin is active - the vulnerable code can be exploited.
-
Confirm Elementor or Beaver Builder integration is in useCheck if the site uses Elementor or Beaver Builder page builders and if the Sales Page Addon functionality is being used on any published pagesAffected if The Sales Page Addon feature is actively used on published pages - injected scripts can execute when visitors view those pages.
You are affected if the Nicheaddons Sales Page Addon plugin is installed, active, and the installed version is 1.4.2 or lower.
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.
From vendor dataUpgrade to version 1.4.6 or later. If no update is available, implement output escaping (esc_html, esc_attr, wp_kses) on all user-controlled data before rendering and consider disabling the plugin until a patch is available.
Fix this in Sales Page Addon
Scoped from the published advisory
- 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-51585 — 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-51585 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