The Pack Elementor AddonsWordPress extension · Webangon
CVE-2025-6550
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 · uneditedThe The Pack Elementor addon plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘slider_options’ parameter in all versions up to, and including, 2.1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 · high confidenceThe Pack Elementor addon plugin for WordPress versions up to 2.1.4 contains a stored XSS vulnerability in the 'slider_options' parameter. Authenticated attackers with Contributor-level access can inject malicious JavaScript payloads that execute whenever users access affected pages due to insufficient input sanitization and lack of proper output escaping.
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 Pack Elementor AddonsWordPress extension
<= 2.1.3CVSS 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.
-
Identify plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Look for 'The Pack Elementor Addons' or 'Webangon The Pack'. The version number is displayed below the plugin name. Alternatively, check the main plugin file (usually /wp-content/plugins/the-pack-elementor-addons/the-pack.php) and look for the 'Version:' header in the file comments.Affected if Version displayed is 2.1.3 or lower
-
Verify affected component is in useAccess Elementor editor on any page/post. Search for 'slider' widgets from The Pack addon. If a slider widget exists, click on it to open the widget settings panel. Look for a 'Slider Options' or similar parameter field in the settings.Affected if A The Pack slider widget with slider_options parameter exists on any published page or is saved in draft
-
Inspect stored slider_options dataCheck the WordPress database. The slider_options values are typically stored in post meta (wp_postmeta table) with meta_key containing 'the_pack_slider' or similar, or in wp_options if theme settings are used. Use phpMyAdmin or WP-CLI: wp post meta list --meta_key=the_pack_slider to find posts using this widget.Affected if Posts or options contain the slider_options meta_key with any stored value
-
Scan for malicious XSS payloadsExamine the stored slider_options values for suspicious patterns. Look for JavaScript event handlers (onclick, onload, onerror), script tags, javascript: URIs, or encoded payloads (like < for <). Query: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%the_pack%' AND (meta_value LIKE '%<script%' OR meta_value LIKE '%onerror=%' OR meta_value LIKE '%javascript:%').Affected if Any stored slider_options value contains JavaScript code, event handlers, or encoded XSS vectors
The environment is affected if The Pack Elementor Addons version is 2.1.3 or lower AND any page uses a slider widget with slider_options parameter containing unsanitized user input.
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 · scopedUpdate The Pack Elementor addon plugin to version 2.1.5 or later. All instances of user-supplied data in slider_options must implement proper input sanitization (such as esc_attr, esc_html) and output escaping before rendering.
2.1.4 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'The Pack Elementor Addons' in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to version 2.1.4 or later
- 5. Alternatively, manually download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin version is 2.1.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in The Pack Elementor Addons
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6550 — 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-2025-6550 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