Sky Addons For ElementorWordPress extension · Wowdevs
CVE-2024-38687
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 wowDevs Sky Addons for Elementor sky-elementor-addons.This issue affects Sky Addons for Elementor: from n/a through <= 2.5.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 confidenceStored Cross-site Scripting (XSS) vulnerability in wowDevs Sky Addons for Elementor allows attackers to inject malicious JavaScript through plugin widgets or features that fail to properly sanitize user input before rendering it in web pages. When authenticated users or visitors access pages containing the malicious payload, the script executes in their browsers.
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
Sky Addons For ElementorWordPress extension
< 2.5.8CVSS 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.
-
Verify Sky Addons for Elementor is installedCheck your WordPress plugins directory or the Elementor widgets panel for 'Sky Addons' presence. In WordPress admin, go to Plugins > Installed Plugins and look for 'Sky Addons for Elementor' or 'Wowdevs Sky Addons'.Affected if The plugin is present in your WordPress installation
-
Determine the installed versionIn WordPress admin, go to Plugins > Installed Plugins, find Sky Addons for Elementor, and note the version number displayed. Alternatively, check the plugin header in the main plugin file (commonly in wp-content/plugins/sky-addons-for-elementor/).Affected if The version number is lower than 2.5.8
-
Confirm Elementor page builder is activeVerify that Elementor Website Builder is installed and active on your WordPress site, as Sky Addons is an Elementor addon that only functions when Elementor is enabled.Affected if Elementor is active and Sky Addons widgets are available for use
-
Identify active Sky Addons widgets on published pagesReview your published pages and posts edited with Elementor. In the Elementor editor, check if any widgets from the Sky Addons category (such as price tables, carousels, or data tables) are present on your site pages.Affected if Any Sky Addons widgets are published and accessible to site visitors or authenticated users
Your site is affected if Sky Addons for Elementor is installed with a version lower than 2.5.8 and any of its widgets are in use on published pages, as the unsanitized user input in those widgets can execute malicious scripts in visitors' browsers.
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 · scoped2.5.8
Update Sky Addons for Elementor to the latest patched version once available. Until then, restrict access to the plugin's editing capabilities to trusted users only and implement Content Security Policy headers to mitigate script execution.
2.5.8 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Sky Addons for Elementor' in the plugin list
- Click 'Update now' if an update is available, or manually download version 2.5.8 or later from a trusted source
- Verify the update completed successfully
- Test the affected functionality to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Sky Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38687 — 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-38687 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