dbcve.org
Ifeature SliderWordPress extension · Cyberchimps

CVE-2022-45375

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to after 1.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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in iFeature Slider plugin <= 1.2 on WordPress.

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 confidence

Authenticated users with contributor+ role can inject malicious JavaScript code through the iFeature Slider plugin settings that gets stored in the database and executes when other users view the affected slider content.

MitigationUpdate iFeature Slider plugin to version greater than 1.2. If no patched version is available, disable the plugin or implement Content Security Policy headers as a defense-in-depth measure.

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
Ifeature SliderWordPress extension
Affected:<= 1.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. Locate the iFeature Slider plugin installation
    Check your WordPress plugins directory for the 'ifeature-slider' or 'cyberchimps-ifeature-slider' folder, or look for the plugin in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder or entry exists in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the iFeature Slider or Cyberchimps iFeature Slider entry. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file header for the 'Version' tag
    Affected if The displayed version number is 1.2 or lower
  3. Verify contributor+ role access to plugin settings
    Check if any user with contributor, author, editor, or administrator role has access to the plugin's settings page (typically under Settings > iFeature Slider or a dedicated Slider menu). Review user roles in Users > All Users and check role capabilities for slider configuration access
    Affected if Contributor or higher role users can access and modify slider settings
  4. Inspect slider settings for suspicious stored content
    Access the plugin's slider management interface and review each slider's content fields (title, description, image URL, link URL, etc.). Check the WordPress database wp_postmeta table for entries where meta_key contains 'slider' and meta_value contains script tags, javascript:, or encoded/encrypted content
    Affected if Any slider settings contain unsanitized JavaScript code, script tags, or unexpected encoded content

You are affected if the iFeature Slider plugin version 1.2 or lower is installed AND contributor-level or higher users can access and modify slider settings, particularly if stored slider content contains script tags or suspicious code.

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 a release after 1.2
Interim mitigation

Update iFeature Slider plugin to version greater than 1.2. If no patched version is available, disable the plugin or implement Content Security Policy headers as a defense-in-depth measure.

Recommended fix Moderate confidence
  1. 1. Navigate to the WordPress admin dashboard and locate the iFeature Slider plugin in the Plugins section.
  2. 2. Check if the plugin has been abandoned or removed from the WordPress plugin repository by searching for 'iFeature Slider' on wordpress.org/plugins.
  3. 3. If the plugin is no longer maintained or no security patch is available, deactivate and delete the iFeature Slider plugin.
  4. 4. Identify an actively maintained alternative slider plugin from the WordPress plugin repository that provides similar functionality.
  5. 5. Install the alternative plugin and recreate any slider content that was using iFeature Slider.
  6. 6. If the plugin must continue to be used, check patchstack.com or wordfence.com for any vendor patches or detailed vulnerability information specific to this CVE.
Caveat The plugin appears to be abandoned with no documented fixed version; replacement with an actively maintained alternative is recommended.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ifeature Slider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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