Comparison SliderWordPress extension · Comparisonslider
CVE-2024-4422
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 Comparison Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the slider title parameter in all versions up to, and including, 1.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber 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 Comparison Slider WordPress plugin is vulnerable to stored XSS via the slider title parameter. Authenticated attackers with subscriber-level access can inject malicious JavaScript due to insufficient input sanitization and output escaping. The injected scripts execute when users access affected pages.
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
Comparison SliderWordPress extension
<= 1.0.5CVSS 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.
-
Confirm plugin installation and versionAccess the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Comparison Slider' or 'Comparisonslider Comparison Slider'. Note the version number displayed. Alternatively, check the plugin's main PHP file (e.g., wp-content/plugins/comparisonslider-comparison-slider/comparison-slider.php) for the 'Version' header in the plugin comment block.Affected if The installed version is 1.0.5 or lower.
-
Check for subscriber-level user accountsNavigate to Users > All Users in the WordPress admin. Review the list of users and identify any accounts assigned the 'Subscriber' role. Also check if any role with limited permissions (subscriber or lower) exists on the site.Affected if Any subscriber-level or lower-privileged user account exists on the site.
-
Inspect stored slider title valuesAccess the plugin settings where sliders are created or managed (typically under a menu item like 'Comparison Slider' or 'Sliders' in the admin sidebar). Review each slider's title field for any suspicious content including HTML tags, JavaScript code, or unusual characters that were not intentionally entered.Affected if Any slider title contains unescaped HTML, script tags, or unexpected JavaScript code that could execute when the slider is rendered.
-
Verify public-facing slider outputVisit pages or posts on the site where Comparison Slider shortcodes or blocks are embedded. View the page source (right-click > View Page Source) and search for the slider title text. Check if it appears as raw HTML or if special characters are properly escaped (e.g., <script> appears as <script>).Affected if The slider title renders as executable HTML or JavaScript instead of being escaped.
The environment is affected if the Comparison Slider plugin version is 1.0.5 or lower AND any subscriber-level user can access the plugin's slider creation interface, allowing them to inject malicious script tags into slider titles that execute when viewed.
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 to version 1.0.6 or later which includes proper sanitization and escaping. Until then, restrict subscriber-level access to the plugin or remove the plugin if no update is available.
Version 1.0.6 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Comparison Slider plugin
- 4. If an update is available, click 'Update Now' to upgrade to the latest version
- 5. Alternatively, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
- 6. Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Comparison Slider
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4422 — 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-4422 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