dbcve.org
Smart Slider 3WordPress extension · Nextendweb

CVE-2022-45845

HIGH · 8.8 CVSS v3.1 Published 2024-01-19
Fix available
A fix is available. Upgrade to 3.5.1.11 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Deserialization of Untrusted Data vulnerability in Nextend Smart Slider 3.This issue affects Smart Slider 3: from n/a through 3.5.1.9.

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 confidence

A deserialization of untrusted data vulnerability in Nextend Smart Slider 3 allows attackers to deserialize malicious data, potentially leading to remote code execution. The vulnerability affects versions up to 3.5.1.9 and stems from insecure handling of serialized input.

MitigationUpdate Smart Slider 3 to version 3.5.1.10 or later. If no patched version is available, audit the plugin's code for deserialization calls (unserialize(), etc.) and implement whitelist-based validation or disable the vulnerable functionality until a fix is released.

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
Smart Slider 3WordPress extension
Affected:< 3.5.1.11

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check Smart Slider 3 installed version
    Navigate to WordPress Admin > Plugins > Installed Plugins > Smart Slider 3 and view the version number, or inspect the plugin's main PHP file (typically nextend-smart-slider3-pro.php or similar) for the 'Version:' header comment
    Affected if The displayed version is below 3.5.1.11 (versions 3.5.1.9 and earlier are affected)
  2. Locate plugin version file directly
    Access the WordPress wp-content/plugins/nextend-smart-slider3/ directory via file manager or FTP and open the primary plugin file or readme.txt to read the Version field
    Affected if The version listed is < 3.5.1.11
  3. Identify deserialization call exposure
    Search the plugin source code for unserialize() function calls, particularly in files handling request parameters or AJAX endpoints. Common locations include frontend controllers or API handlers within the plugin directory
    Affected if The plugin contains unserialize() calls that process input from user-supplied parameters without validation (the vulnerable code pattern)
  4. Verify plugin is active on public-facing site
    Confirm via WordPress admin that the Smart Slider 3 plugin is both installed and activated, and check that slider shortcodes or widgets are published on visible pages
    Affected if The plugin is active and its sliders are rendered on the site, allowing unauthenticated attackers to potentially send malicious serialized payloads

You are affected if Smart Slider 3 version is below 3.5.1.11 and the plugin is active with unserialize() calls handling external input on your site.

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 3.5.1.11 or later
Fixed in 3.5.1.11
Interim mitigation

Update Smart Slider 3 to version 3.5.1.10 or later. If no patched version is available, audit the plugin's code for deserialization calls (unserialize(), etc.) and implement whitelist-based validation or disable the vulnerable functionality until a fix is released.

Recommended fix High confidence

Smart Slider 3 version 3.5.1.11

  1. Backup your WordPress site before making any changes
  2. Navigate to Dashboard > Plugins in your WordPress admin panel
  3. Locate Smart Slider 3 in the plugins list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. If automatic updates are not showing, manually download Smart Slider 3 version 3.5.1.11 from the official WordPress repository or the vendor's website
  6. Deactivate and delete the existing Smart Slider 3 plugin, then upload and install version 3.5.1.11
  7. After updating, verify the plugin is running version 3.5.1.11 or higher

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

Fix this in Smart Slider 3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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